NousResearch/hermes-agent

FTS index rebuild retry and write-stall alerting

Cluster 114266. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #114854 on 18 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #114854. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114854. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #114854, then check it covers your case.

Read #114854 Pick up a Lab task

These items concern a gateway bug where a failed full-text-search index rebuild was permanently abandoned for the process lifetime, and a related scenario where transcript writes silently stalled for an extended period without surfacing errors. The fixes introduce cooldown-based rebuild retries and escalate stalled appends to ERROR level.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#114854 fix(gateway): FTS rebuild retries on a cooldown instead of giving up for the process lifetime; stalled transcript appends escalate to ERROR (#114266, salvage #114301)

merged to main

files: gateway/run.py, gateway/run_turn_runner.py, gateway/session.py, gateway/session_transcript.py, gateway/shutdown_flush.py, tests/gateway/test_cached_agent_history_guard.py, tests/gateway/test_pending_queue_spool.py, tests/gateway/test_session.py, tests/gateway/test_session_db_corrupt_fallback.py, tests/gateway/test_session_db_replaced_fallback.py

1 PR closed without merging

From the close comments: merged via another change 1

#114301 fix(gateway): retry FTS index rebuild after cooldown instead of giving up permanently · merged via another change → f2755ae, #114854, #114266, #114301

Closed issues · 1

Closed#114266[Bug] Silent 11-day total write-outage on live session (disk=0, memory growing) — state.db stops advancing while gateway keeps answering, no alert ever surfaced

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 1.00: 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

Merged PRs: #114854
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114266.json
cluster/114266.md