Nothing open on GitHub. Fix merged in #100972 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #100972. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #100972. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members concern a bug where follow-up messages queued during gateway busy or compression windows are silently dropped with no logging or recovery. The work addresses rescuing or surfacing those orphaned queue entries.
Open issues0
Open PRs0
Fixes on record
-
#100972 Gateway follow-ups queued during a busy/compression window no longer vanish; overflow survives shutdown (#99882, salvage #99912)
files:
gateway/run.py,gateway/shutdown_flush.py,tests/gateway/test_fifo_overflow_rescue.py,tests/gateway/test_shutdown_flush.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#99912 fix(gateway): rescue orphaned FIFO overflow when session goes idle (#99882) · merged via another change →
#100972
Closed issues · 1
- Closed#99882[Bug]: Queued follow-ups (demoted to queue during context compression) are silently orphaned — messages lost, no log
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
- #100972
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026