Frame worker messages without treating newlines as boundaries
A diagnostic string contains a newline and splits one response into two apparent messages.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Binary protocols · Input validation
Estimated field mix
- Systems programming70%
- API design30%
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
- Frame declares version, type, request identity, and bounded payload length
- Reader handles partial headers and payloads
- Unknown versions fail without consuming the next frame
Implementation constraints
- Cap frame size before allocating its payload buffer.
Verification to include
- Read several frames split across every header boundary.
- Advertise an oversized or truncated payload and verify bounded rejection.
Deliverables
- Versioned frame codec and fragmentation tests
Rollout and recovery
Keep the line protocol available only for old local fixtures during 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.