Nothing open on GitHub. Fix merged in #101725 on 2 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #101725. 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 all concern a performance optimization to prevent cron-sourced sessions from being included in the trigram full-text search index. The goal is to avoid unnecessary index inflation caused by cron runs.
Open issues0
Open PRs0
Fixes on record
-
#101725 perf(state): exclude cron sessions from the trigram FTS index (salvage #101266)
files:
hermes_state_common.py,hermes_state_schema.py,hermes_state_search.py,tests/state/test_fts_trigram_cron_exclusion.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#101266 perf(state): keep cron runs from inflating the trigram index · merged via another change →
593aa74,#101725
Closed issues · 1
- Closed#101199perf(state): exclude cron-source sessions from trigram FTS index (messages_fts_trigram_src)
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
- #101725
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026