TUI gateway orphan-reap interrupt flag not cleared on reattach
Cluster 104160. Data as of
Nothing open on GitHub. Fix merged in #104924 on 7 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 #104924. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104924. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests concern a bug in the TUI gateway where an orphan-reap interrupt sentinel is not cleared when a session re-attaches, causing subsequent operations to receive 4009 errors until the idle reap runs. The members focus on identifying and fixing this flag-clearing behavior.
Open issues0
Open PRs0
Fixes on record
-
#104924 fix(tui-gateway): reconnect after abandoned orphan interrupts (salvage #104186)
files:
evals/liveness/ws_orphan_reconnect.py,tests/tui_gateway/test_ws_orphan_races.py,tui_gateway/session_lifecycle.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#104160TUI gateway: orphan-reap interrupt flag never cleared when another writer un-detaches the session → every resume/activate/prompt.submit gets 4009 until idle reap
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
- #104924
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 7 Sep 2026