Close inherited descriptors before executing the worker
A child inherits the supervisor listener and keeps it open after the parent exits, preventing clean restart.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Process spawning · Resource cleanup
Estimated field mix
- Systems programming70%
- Security30%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Child receives only declared stdin, stdout, stderr, and control handles
- Supervisor closes duplicate ends after spawn
- Restart can bind the same local endpoint
Implementation constraints
- Do not depend on a global close-all scan that races other threads opening handles.
Verification to include
- Spawn, complete, and restart a worker while checking descriptor counts.
- Add an undeclared inheritable handle and confirm the fixture detects it.
Deliverables
- Spawn handle policy and leak regression
Rollout and recovery
Audit handle inheritance before enabling multiple workers.
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.