Gateway self-kill via cgroup cleanup prevention
Cluster 126845. Data as of
Nothing open on GitHub. Fix merged in #130518 on 1 Oct 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 #130518. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #130518. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the cgroup_cleanup reaper kills the gateway process when the gateway is running inside its own cgroup, along with proposed or submitted fixes to refuse cgroup cleanup in that scenario.
Open issues0
Open PRs0
Fixes on record
-
#130518 fix(gateway): stop the cgroup cleanup reaper from killing a live gateway (#126845, salvage #126846)
files:
contributors/emails/[email protected],gateway/cgroup_cleanup.py,tests/gateway/test_cgroup_cleanup.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#126845[Bug]: cgroup_cleanup reaper self-kills the gateway when run from inside its own cgroup (terminal tool / agent child)
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
- #130518
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Oct 2026