Session DB message duplication and compression rollback fixes
Cluster 99477. Data as of
Nothing open on GitHub. Fix merged in #100427 on 1 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #100427. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #100427. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug causing exponential message duplication in the session database when compression interrupts queued drains, along with fixes to roll back the live transcript when an in-place compaction commit fails. Includes a defense-in-depth deduplication backstop as a secondary safeguard.
Open issues0
Open PRs0
Fixes on record
-
#100427 fix(compression): roll the live transcript back when an in-place compaction commit fails (#99477)
files:
agent/conversation_compression.py,tests/run_agent/test_in_place_commit_rollback_99477.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · other 1
Closed issues · 1
- Closed#99477[Bug]: Exponential message duplication in session DB when compression interrupts queued follow-up drain
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.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
- #100427
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Sep 2026