Cairn
NousResearch/hermes-agent

Systemd gateway PID detection and relaunch fix

Cluster 66900 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address how hermes update handles systemd-managed gateways whose MainPID belongs to a wrapper process (e.g. doppler run), resolving incorrect PID resolution and unintended killing of freshly-restarted gateway services.

Open issues1

  • Issue#66900hermes update relaunches systemd-managed gateways as detached --replace processes when the unit MainPID is a wrapper (e.g. doppler run)

Open PRs2

  • PR#66913fix(gateway): resolve service-managed gateway PID when ExecStart is wrapped (#66900)
  • PR#119646fix(gateway): count a service job's gateway descendants as service PIDs (#105938)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/66900.json
cluster/66900.md