Cairn
NousResearch/hermes-agent

FTS index corruption fixes across SQLite upgrades

Cluster 86027 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These items address malformed or incompatible full-text search indexes that arise when upgrading SQLite versions, adding detection and self-repair logic during engine changes or index rebuilds.

Open issues1

  • Issue#86027[Bug]: Legacy messages_fts_trigram from SQLite 3.46.1 is reported malformed by SQLite 3.53.4 during v0.18.2 → v0.20.1 upgrade

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: PR volume cleanup 1 · done elsewhere 1

  • #86062 fix(state): recover from malformed legacy FTS index during rebuild · done elsewhere
  • #86183 fix(state): verify and self-repair FTS5 indexes on engine change · PR volume cleanup → 1c68b13, 693c0e1
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.00 means 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 Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/86027.json
cluster/86027.md