feat(sandbox): PID 1 process tree lifecycle and ownership reaper #6
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
Reference
Ting/workflows#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
Make workflow process-tree cleanup bounded and ownership-safe, including orphan reaping and timeout termination.
Design
Run the sandbox with PID 1 semantics so the kernel can orphan-reap descendants. Watch wall-clock deadlines and use
instance.nuownership records to signal only proven run-root PIDs, escalating from SIGTERM to SIGKILL after five seconds.Tasks
--unshare-pidand PID 1 orphan reaping.instance.nuownership law (signal only proven run-root PIDs; SIGTERM, five-second grace, then SIGKILL).Gherkin Specification Delta
must.contracts.ting-workflows.executor.process-tree-reaper
Scenario: Reap a timed-out workflow process tree
Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).