Compression dispatch incorrectly resetting summary idle timeout
Cluster 114938 · agent. Data as of
1 open item. Fix merged in #116746 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116746. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116746. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
Multiple fixes addressing a bug where compression dispatch operations were incorrectly resetting the summary idle fence/timeout. A related fix also ensures slow local summaries can finish streaming.
Open issues0
Open PRs1
- PR#113654fix(compression): let slow local summaries finish streaming
Fixes on record
-
#116746 fix(compression): a dispatch-only provider failure no longer resets the summary idle fence (#114938, salvage #115683)
files:
agent/auxiliary_client.py,tests/agent/test_aux_progress_streaming.py,tests/agent/test_aux_relay_progress_seam.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#114938Compression dispatch falsely resets the summary idle timeout
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.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
- Subsystem
- agent
- Merged PRs
- #116746
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026