Fix stale WAL checkpoint corrupting state.db at shutdown
Cluster 105670. Data as of
Nothing open on GitHub. Fix merged in #106315 on 9 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 #106315. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #106315. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug allowed handles that had lost their WAL generation to perform a checkpoint into state.db during graceful shutdown, potentially corrupting it. These issues and fixes add guards to skip or block that stale checkpoint when the WAL generation has been replaced or deleted.
Open issues0
Open PRs0
Fixes on record
-
#106315 fix(state): a handle that lost its WAL generation no longer checkpoints stale frames into state.db at shutdown (#105670; salvage #105692, dup #105686)
files:
hermes_state.py,hermes_state_schema.py,tests/hermes_state/test_deleted_wal_checkpoint_guard.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#105670WAL generation split-brain: DeletedWalGenerationError guarded writes, but the graceful-shutdown checkpoint then corrupted state.db (field report)
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 LabAt a glance
- Merged PRs
- #106315
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 9 Sep 2026