Session search FTS broken in read-only cross-profile mode
NousResearch/hermes-agent · cluster 49554 · agent
Data as of
2 open items. Fix attempted, not merged.
The short answer
2open issues
0open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 2 issues and 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes address session_search returning zero results when using read-only database connections, because FTS5 was never enabled for them, and the profile parameter was not being forwarded through handler calls.
Open issues2
Open PRs0
3 PRs closed without merging
From the close comments: superseded by another PR 2 · duplicate 1
-
#54869 fix(session_search): detect FTS capability on read-only connections · duplicate →
#49577 -
#60792 fix(agent,state): pass profile in session_search handlers + enable FTS in read-only mode · superseded by another PR →
a9838c2,57197cd,#60789 -
#60819 fix(agent): forward profile param in session_search handler calls · superseded by another PR →
a9838c2,57197cd,#60789
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.54: 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
- Closed issues
- 0
- Attempts
- 3 PRs closed without merging