Greptile P2 on PR #893. A max-uptime callback may already be running when Release stops its timer. If Release deletes the teardown entry before that callback reaches claimTeardown, the callback recreates an unclosed entry, repeats stop/remove on the already-released container, and leaves the entry in the map permanently because the reaper no longer calls forgetTeardown.
The merged fix (#893) closed the reaper-vs-Release double teardown; this is the remaining ordering hole on the other side. Needs a terminal state that a started callback cannot resurrect.
Source: internal/container/pool.go around claimTeardown/forgetTeardown.
Close reason
Landed: the max-uptime reaper no longer resurrects teardown state after Release; entry creation and timer recording share one critical section, and the claim path is lookup-only.
Imported from beads archie-core-vax0 · GitHub #919 · type bug · priority P2 · created 2026-09-19 · closed 2026-09-21
Greptile P2 on PR #893. A max-uptime callback may already be running when Release stops its timer. If Release deletes the teardown entry before that callback reaches claimTeardown, the callback recreates an unclosed entry, repeats stop/remove on the already-released container, and leaves the entry in the map permanently because the reaper no longer calls forgetTeardown.
The merged fix (#893) closed the reaper-vs-Release double teardown; this is the remaining ordering hole on the other side. Needs a terminal state that a started callback cannot resurrect.
Source: internal/container/pool.go around claimTeardown/forgetTeardown.
### Close reason
Landed: the max-uptime reaper no longer resurrects teardown state after Release; entry creation and timer recording share one critical section, and the claim path is lookup-only.
---
_Imported from beads `archie-core-vax0` · GitHub #919 · type bug · priority P2 · created 2026-09-19 · closed 2026-09-21_
sam
added the bugmedium labels 2026-10-27 13:41:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Greptile P2 on PR #893. A max-uptime callback may already be running when Release stops its timer. If Release deletes the teardown entry before that callback reaches claimTeardown, the callback recreates an unclosed entry, repeats stop/remove on the already-released container, and leaves the entry in the map permanently because the reaper no longer calls forgetTeardown.
The merged fix (#893) closed the reaper-vs-Release double teardown; this is the remaining ordering hole on the other side. Needs a terminal state that a started callback cannot resurrect.
Source: internal/container/pool.go around claimTeardown/forgetTeardown.
Close reason
Landed: the max-uptime reaper no longer resurrects teardown state after Release; entry creation and timer recording share one critical section, and the claim path is lookup-only.
Imported from beads
archie-core-vax0· GitHub #919 · type bug · priority P2 · created 2026-09-19 · closed 2026-09-21