Desktop SSH backend cleanup and lock handling
Cluster 132034 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #132470 on 7 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #132470. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132470. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where superseded desktop SSH serve backends are not properly reaped when their locks are overwritten, potentially causing a reconnect storm that leaks detached backends until the remote host runs out of memory. The accompanying fixes address lock retirement and backend cleanup logic.
Open issues0
Open PRs0
Fixes on record
-
#132219 SSH-isolated backends retire once a newer Desktop spawn owns the lock (#132034)
files:
hermes_cli/dashboard_procs.py,hermes_cli/main.py,hermes_cli/web_server.py,hermes_cli/web_server_owner_exit.py,hermes_cli/web_server_skew_exit.py,tests/hermes_cli/test_resource_limits.py,tests/hermes_cli/test_web_server_owner_exit.py,tests/hermes_cli/test_web_server_ws_ping.py -
#132470 fix(desktop): Windows SSH host locks let a superseded backend retire [risk 0.30]
files:
hermes_cli/windows_ssh_runtime.py,tests/hermes_cli/test_web_server_owner_exit.py,website/docs/user-guide/configuration.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#132703 fix(serve): reap superseded desktop-ssh backends whose lock was overwritten (fixes #132034) · done elsewhere →
7533bd2,503a6b6,#132034,#132219,#132470
Closed issues · 1
- Closed#132034[Bug]: Desktop SSH reconnect storm leaks detached serve backends until the remote OOMs
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.50: 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 Lab