FTS index corruption handling in state.db
Cluster 133375 · agent. Data as of
Nothing open on GitHub. Fix merged in #134721 on 7 Oct 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 #134721. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #134721. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how corrupt full-text-search indexes in state.db are detected and handled, covering error catching inside rebuild passes and related data-loss concerns during rebuilds. No resolution status is assumed.
Open issues0
Open PRs0
Fixes on record
-
#134721 fix(state): a corrupt FTS index no longer aborts the session-search rebuild and optimize passes (#133375, salvage #133400)
files:
hermes_state_search.py,tests/hermes_state/test_fts_rebuild_corruption_class.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#133400 fix(state): catch the corruption-class DatabaseError inside rebuild_fts() · done elsewhere →
daa9593,#134721
Closed issues · 1
- Closed#133375state.db FTS corruption leads to ~14h of silent data loss: one-shot rebuild, repair-only-on-open, in-memory retry queue
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
- agent
- Merged PRs
- #134721
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Oct 2026