Fix background job cleanup keyed by owner not container
Cluster 120630. Data as of
Nothing open on GitHub. Fix merged in #121380 on 24 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 #121380. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #121380. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where /stop, /new, and the inactivity watchdog were failing to reap abandoned turn background jobs because cleanup was keyed on container rather than owner. The fix changes job reaping to use owner identity instead.
Open issues0
Open PRs0
Fixes on record
-
#121380 /stop and /new reap a turn's background jobs by owner (#120630, salvage #120631)
files:
tests/gateway/test_abandoned_turn_process_cleanup.py,tests/tools/test_oneshot_completion_linger.py,tools/process_registry.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#120631 fix(gateway): reap an abandoned turn's background jobs by owner, not container key · done elsewhere →
c2e0a74
Closed issues · 1
- Closed#120630[Bug]: /stop, /new and the inactivity watchdog never reap the abandoned turn's background jobs (container key vs owner id)
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
- #121380
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Sep 2026