CLI update SIGKILL timing causes PTY/WAL shutdown issues
Cluster 111912. Data as of
Nothing open on GitHub. Fix merged in #112266 on 16 Sep 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 #112266. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112266. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where the CLI's update process sends SIGKILL too early during dashboard shutdown, orphaning PTY child processes and triggering WAL-related fatal errors on restart. The work involves adjusting kill timeouts to allow cleaner teardown.
Open issues0
Open PRs0
Fixes on record
-
#112266 fix(cli): hermes update no longer SIGKILLs a manual dashboard mid-shutdown and orphans its WAL-holding PTY children (#111912, salvage #111916)
files:
hermes_cli/dashboard_procs.py,tests/hermes_cli/test_dashboard_procs_kill_grace.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#111916 fix(cli): increase dashboard kill timeout to prevent PTY child leaks … · merged via another change →
f93d33f,#112266
Closed issues · 1
- Closed#111912[Bug]: FATAL `DeletedWalGenerationError` on startup due to premature SIGKILL during update
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
- #112266
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026