hermes update respawns orphan serve backends bug
Cluster 78821 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #86683 on 15 Aug 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 #86683. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86683. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where hermes update unintentionally respawns orphaned hermes serve --port 0 backend processes, causing them to accumulate across updates. The members include the bug report and two related fix attempts.
Open issues0
Open PRs0
Fixes on record
-
#86683 fix(cli): stop hermes update from respawning orphan serve --port 0 backends (salvage #78879)
files:
hermes_cli/dashboard_procs.py,hermes_cli/main.py,tests/hermes_cli/test_update_stale_dashboard.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#78879 fix(cli): stop hermes update from respawning orphan serve --port 0 (#78821) · merged via another change →
#86683
Closed issues · 1
- Closed#78821[Bug]: hermes update respawns every orphan `hermes serve --port 0`, accumulating backends across updates
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
- Subsystem
- hermes cli
- Merged PRs
- #86683
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Aug 2026