NousResearch/hermes-agent
FTS corruption detection gaps in health probe
Cluster 100227 · hermes cli. Data as of
2 open items. Fix attempted, not merged.
The short answer
0open issues
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes address cases where segment-dependent or content-dependent FTS trigram index corruption goes undetected by the health probe and repair tooling. The work focuses on improving the probe's ability to surface these corruption scenarios rather than silently missing them.
Open issues0
Open PRs2
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#100263 fix(state): detect content-dependent FTS index corruption in the health probe · superseded by another PR →
#100239
Closed issues · 1
- Closed#100227[Bug]: _db_opens_cleanly / hermes doctor miss segment-dependent FTS trigram corruption; sessions repair says 'no repair needed' while every message write 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
- Subsystem
- hermes cli
- Closed issues
- 1
- Attempts
- 1 PR closed without merging