Fresh state.db FTS setup corruption and serialization fixes
Cluster 105790. Data as of
Nothing open on GitHub. Fix merged in #106311 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 #106311. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #106311. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where a freshly created state.db becomes corrupted during full-text search bootstrap, and several fixes aimed at serializing or locking the FTS setup process to prevent concurrent corruption.
Open issues0
Open PRs0
Fixes on record
-
#106311 fix(sessions): a fresh state.db no longer publishes FTS tables before owning the rebuild lock (#105790; salvage #105805)
files:
hermes_state_schema.py,tests/state/test_fts_fresh_bootstrap_admission.py
2 PRs closed without merging
From the close comments: closed without comment 1 · done elsewhere 1
Closed issues · 1
- Closed#105790[Bug] Fresh state.db corrupted within ~70 min of creation by gateway's own FTS setup — quick_check passes, integrity_check cannot prepare, doctor surgery fails
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
- #106311
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 9 Sep 2026