Nothing open on GitHub. Fix merged in #82719 on 9 Aug 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 #82719. 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.
These items concern a scenario where a corrupt state.db causes FTS rebuilds to falsely report success, leading to silent data loss as the pending queue rotates transcripts away. The group covers the problem report and related fixes addressing write path verification and handling of pending-cap overflow.
Open issues0
Open PRs0
Fixes on record
-
#82719 fix(state): keep canonical writes available when FTS is corrupt (#78182)
files:
hermes_state.py,hermes_state_common.py,hermes_state_schema.py,hermes_state_search.py,tests/state/test_fts_runtime_rebuild.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#78323 fix(state): verify FTS rebuild write path; spool pending-cap overflow · superseded by another PR →
#82719,#84785
Closed issues · 1
- Closed#78182Gateway writes through a corrupt state.db indefinitely: one-shot FTS rebuild reports success without verifying the write path, then the 200-cap pending queue silently rotates transcripts away
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
- Merged PRs
- #82719
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 9 Aug 2026