Correlate out-of-order worker replies to the right caller
Two conversions finish in reverse order and the supervisor resolves the first waiter with the second result.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Correlation IDs · Concurrency
Estimated field mix
- Systems programming70%
- Distributed systems30%
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
- Every accepted request has a unique operation identity
- Replies resolve only the matching pending request
- Duplicate and unknown replies are recorded without completing another caller
Implementation constraints
- Keep the pending map bounded by admission capacity and deadlines.
Verification to include
- Complete three requests in reverse order and verify each result.
- Send a duplicate and an unknown identity and confirm pending callers remain unchanged.
Deliverables
- Correlation table and ordering tests
Rollout and recovery
Enable concurrent requests only after correlation checks pass.
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.