SessionDB corruption quarantine and shutdown safety
Cluster 101093. Data as of
Nothing open on GitHub. Fix merged in #101118 on 2 Sep 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 #101118. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101118. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where a structurally corrupt state.db could have WAL checkpoint data written to wrong page numbers, and introduce quarantining of the corrupt SessionDB handle to prevent further damage, along with quiescing the thread pool before closing state.db at shutdown.
Open issues0
Open PRs0
Fixes on record
-
#101118 fix(gateway): quiesce the thread pool before closing state.db at shutdown
files:
gateway/run.py,tests/gateway/test_shutdown_executor_quiesce.py -
#101224 fix(state): quarantine SessionDB handle after structural corruption (salvage of #101095)
files:
contributors/emails/[redacted:email],docs/state-db-recovery.md,gateway/session.py,hermes_state.py,run_agent.py,tests/gateway/test_session_db_corrupt_fallback.py,tests/hermes_state/test_state_db_corrupt_quarantine.py,tests/run_agent/test_flush_diverts_on_corrupt_state_db.py,tests/run_agent/test_turn_completion_explainer.py,tests/state/test_fts_runtime_rebuild.py,tests/test_state_db_notadb_fail_closed.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#101095 fix(state): quarantine SessionDB handle after structural corruption (no retry, no close-time checkpoint) · merged via another change →
#101224,#101093
Closed issues · 1
- Closed#101093[Bug]: close-time WAL checkpoint on a structurally corrupt state.db wrote 15 pages to wrong page numbers (page 1 <- FTS trigram leaf)
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 Lab