You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Keep Email backup cleanup owned by its parent shell #5824
The Email backup refresh can lose its temporary workspace after stopping its completion watches. This blocks recovery checks and currently fails CI on #5820.
Steps to Reproduce
The native full Go regression in run 41607447333 failed the foreign unfinished-job control: the completion readback could not open its temporary file because its directory had disappeared.
Exercise the actual cleanup handler from a child process in the inherited-handler state, then verify the parent workspace still exists.
Expected Behavior
Only the owning parent shell may stop its watches or remove its workspace. Completed snapshot and mirror proof must remain required.
Actual Behavior
Cleanup has no process-owner fence. A cancelled watch can inherit the parent's exit trap before resetting it, matching the Bash maintainer's documented fork/termination race. The observed CI failure is consistent with that mechanism; a deterministic child-cleanup control is required.
Acceptance Criteria
A real child executing the inherited cleanup handler preserves the parent's workspace and watch.
Parent cleanup still stops and reaps its watch and removes its workspace.
Existing source, owner, completion, mirror and privacy refusals still pass.
Full native CI passes and the reviewed repair is delivered.
#5541 - feat(email): prepare recoverable storage keys with current backups [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 3, 2026
🔗 Related PRs
#5541 - feat(email): prepare recoverable storage keys with current backups [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #5824 nonce=7ea5a659a87189992927dbef4e5831c0