NousResearch/hermes-agent

SQLite connection close-then-untrack ordering fixes

Cluster 75629. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #75883 on 1 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #75883 Pick up a Lab task

Multiple fixes addressing a race/ordering bug where SQLite connections were untracked before close succeeded, leaving guards in an incorrect state. Changes enforce that untracking only happens after a successful close.

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.

#75883 fix(state): four session-state fixes — safe close tracking, flush-cursor class fix, row-retry, usage-PK healer

merged to main

files: agent/context_compressor.py, agent/turn_finalizer.py, contributors/emails/[redacted:email], contributors/emails/[redacted:email], hermes_cli/sqlite_safe_read.py, hermes_state.py, hermes_state_schema.py, tests/agent/test_micro_compaction.py, tests/agent/test_turn_finalizer_final_response_persistence.py, tests/run_agent/test_identity_flush.py, tests/state/test_no_more_rows_retry.py, tests/state/test_session_model_usage_pk_heal.py, tests/test_sqlite_lock_safe_inspection.py

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

#75699 fix(cli): untrack sqlite connections only after close succeeds · merged via another change → #75883, #75629
#75709 fix(sqlite): close connection before untracking on failure (#75629) · duplicate → #75699

Closed issues · 1

Closed#75629[Bug]: sqlite_safe_read untracks a connection before closing it, so a failed close leaves the byte-probe guard believing nothing is live

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.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: #75883
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 1 Aug 2026

For your agent

The same facts, typed.

cluster/75629.json
cluster/75629.md