Separate protocol output from worker diagnostics
A library warning written to stdout is parsed as a reply and closes the worker connection.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Process I/O · Diagnostics
Estimated field mix
- Systems programming70%
- Developer tooling30%
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
- Protocol frames use one declared channel
- Diagnostics use stderr with bounded capture
- Malformed protocol bytes fail the request without hiding diagnostics
Implementation constraints
- Sanitize diagnostics and cap retained bytes per worker.
Verification to include
- Return a valid response while writing warnings to stderr.
- Write nonprotocol bytes on the protocol channel and verify isolated failure.
Deliverables
- Channel contract and mixed-output fixtures
Rollout and recovery
Treat unexpected stdout as a worker defect during local migration.
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.