FTS5 shadow table orphan bug and repair handling
Cluster 103840 · agent. Data as of
Nothing open on GitHub. Fix merged in #108130 on 11 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 #108130. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where database recovery resurrects orphaned FTS5 shadow tables causes startup failures; related fixes and improvements address detection, self-healing, and repair of these orphan tables on session database open.
Open issues0
Open PRs0
Fixes on record
-
#108130 state.db FTS damage no longer kills turns; doctor/repair/recover handle real incident shapes (#97794, #88587, #100227, #103840, #106667, #102240, #98050, #103647, #96591, #105887; salvage #97843 #88604 #56824 #91413 #102808 #103657 #106890 #103321)
files:
agent/turn_explainers.py,contributors/emails/[email protected],contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],gateway/run_notifications.py,hermes_cli/console_engine.py,hermes_cli/doctor_state.py,hermes_cli/session_lost_and_found.py,hermes_cli/session_recovery.py,hermes_cli/sessions_cmd.py,hermes_cli/web_routers/_common.py,hermes_cli/web_routers/analytics.py,hermes_cli/web_server_sessions.py,hermes_constants.py,hermes_state_errors.py,hermes_state_fts.py,hermes_state_repair.py,hermes_state_schema.py,hermes_state_search.py(+12 more)
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#103840[Bug]: state.db recovery via `.recover` resurrects orphan FTS5 shadow tables — gateway fails startup with "fts5: error creating shadow table messages_fts_data: table already exists"
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
- Subsystem
- agent
- Merged PRs
- #108130
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 11 Sep 2026