Gateway restart fallback behavior under systemd units
Cluster 126474. Data as of
Nothing open on GitHub. Fix merged in #130521 on 3 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #130521. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #130521. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how gateway restart fallback behaves when the gateway is managed by a legacy or non-standard named systemd unit, including cgroup placement, force-kill timing, and conditions under which the fallback should be refused.
Open issues0
Open PRs0
Fixes on record
-
#130521 hermes gateway restart no longer takes over a gateway run by a legacy or custom-named systemd unit (#126474, salvage #126578)
files:
hermes_cli/gateway.py,tests/hermes_cli/test_gateway_restart_external_supervisor.py
1 PR closed without merging
From the close comments: closed without comment 1
- #126578 fix(gateway): refuse restart fallback when gateway is service-managed under any unit name · closed without comment
Closed issues · 1
- Closed#126474gateway restart fallback: replacement spawned in caller's cgroup + 5s force-kill of busy gateway (nonstandard unit name)
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.00means 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 LabAt a glance
- Merged PRs
- #130521
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026