Cairn

Compression cooldown rollback crashes on missing session row

NousResearch/hermes-agent · cluster 106271

Data as of

Nothing open on GitHub. Fix merged in #106522. Check it covers your case.

The short answer

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

These issues and PRs address a bug where the compression failure-cooldown rollback raises an error instead of gracefully tolerating a missing or deleted session row, which can crash the turn dispatcher. The fixes make the rollback logic handle the absent row without raising.

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.

  • #106522 fix(state): compression cooldown rollback no longer crashes the turn when the session row vanished (#106271, salvage #106276)

    merged to main

    files: hermes_state_compression.py, tests/agent/test_compression_concurrent_fork.py

3 PRs closed without merging

From the close comments: merged via another change 2 · superseded by another PR 1

  • #106276 fix(state): tolerate a vanished session row in compression cooldown rollback · merged via another change → 8a50413, #106522, #106271
  • #106277 fix(compression): tolerate deleted cooldown sessions · merged via another change → 8a50413, 17fe7bc, #106522, #106271
  • #106278 fix(state): tolerate missing session row in compression cooldown rollback (#106271) · superseded by another PR → #106276
Closed issues · 1
  • Closed#106271Compression failure-cooldown rollback raises instead of tolerating a missing session row (turn-dispatcher crash)
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.40: 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
#106522
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
9 Sep 2026

For your agent

The same facts, typed.

cluster/106271.json
cluster/106271.md