Block or fix state DB repair with deleted WAL holders
Cluster 97329. Data as of
Nothing open on GitHub. Fix merged in #101667 on 2 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 #101667. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101667. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where state.db schema repair proceeds incorrectly when a deleted WAL generation still has active holders, and introduce fixes to refuse or block repair in that scenario.
Open issues0
Open PRs0
Fixes on record
-
#101667 fix(state): refuse schema repair while a deleted WAL generation is still held (salvage #97330)
files:
contributors/emails/[email protected],contributors/emails/[redacted:email],hermes_state.py,hermes_state_holders.py,tests/state/test_fts_runtime_rebuild.py,tests/state/test_state_db_holders.py,tests/test_state_db_repair_live_writer_guard.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#97330 fix(state): block repair on deleted SQLite holders · merged via another change →
#101667
Closed issues · 1
- Closed#97329[Bug]: state.db repair misses holders on deleted WAL generation
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
1.00: 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
- #101667
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026