Recovery path when WAL guard fires
Cluster 110054 · apps/desktop. Data as of
1 open item. Fix merged in #121428 on 24 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #121428. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #121428, then check whether your report is the one still open.
Read #121428Pick up a Lab taskA reported pain point where users have no in-product recovery after the deleted-WAL guard triggers, plus two related fixes addressing recovery flow and correct HTTP status codes in that scenario.
Open issues1
- Issue#110054Pain cluster: after the deleted-WAL guard fires there is no in-product recovery — Desktop users restart/ask-the-agent/run doctor --fix and make it worse (4 Discord threads, 13 issues this week)
Open PRs0
Fixes on record
-
#121428 fix(dashboard): return 503, not 500, for a deleted WAL or replaced state.db
files:
hermes_cli/web_routers/_common.py,hermes_cli/web_routers/sessions.py,tests/hermes_cli/test_web_analytics_corrupt_store.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#110073 fix(state): in-product recovery after deleted-WAL guard fires (#110054) · done elsewhere →
4cc4072,#121428,#110054
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
- apps/desktop
- Merged PRs
- #121428
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Sep 2026