Terminate a process tree without signaling unrelated work
A timed-out worker launches a helper. Killing only the parent leaks the helper; reusing a process-group identifier risks signaling a newer process.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Process groups · Identity fencing · Cleanup
Estimated field mix
- Systems programming60%
- Security40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional document converter launches local sandbox substitutes as child processes. Its prototype parses newline-delimited output, leaks descriptors, and retries requests after ambiguous worker exits. Create a Rust supervisor and deterministic worker fixtures; no document content or production sandbox is supplied.
Setup prerequisites
- File descriptors
- Framing
- Process signals
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Each operation owns a fresh supervised process group or platform job object
- Termination verifies the group identity before signaling
- Cleanup observes all declared descendants or reports unresolved members
Implementation constraints
- Tests use inert local helpers and never enumerate or signal arbitrary host processes.
Verification to include
- Terminate a fixture parent and its two waiting children.
- Reuse a synthetic numeric identifier and prove identity validation blocks the stale cleanup.
Deliverables
- Process-tree lifecycle adapter and safe termination tests
Rollout and recovery
Keep worker concurrency at one until descendant cleanup is reliable.
Value of the work
For the engineer: Practice IPC contracts, resource inheritance, process supervision and ambiguous completion.
For the team: Review a local worker boundary that contains crashes and preserves request outcomes before connecting an isolated execution provider.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.