Define queue ownership before starting worker threads
Workers borrow configuration from a stack-owned builder that disappears after start, while the queue handle can outlive the pool.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Ownership · Thread lifecycle
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 image-indexing utility runs CPU-only synthetic jobs through a Rust worker pool. Its prototype loses wakeups, blocks shutdown, and treats cancellation as completion. Build a local library and deterministic concurrency harness; image content, GPU work, and production deployment are excluded.
Setup prerequisites
- Mutexes and condition variables
- Atomics
- Thread lifecycle
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Pool-owned state outlives every worker
- Queue handles cannot submit after terminal shutdown
- Dropping the final handle has documented behavior
Implementation constraints
- Avoid leaked static references and process-wide mutable state.
Verification to include
- Create, submit, join, and drop a pool repeatedly under a leak checker.
- Drop external handles in different orders and verify workers cannot access released state.
Deliverables
- Ownership diagram and lifecycle tests
Rollout and recovery
Keep the single-thread runner until lifecycle checks pass.
Value of the work
For the engineer: Practice happens-before reasoning, ownership transfer, cancellation and liveness testing.
For the team: Review a worker primitive whose overload and shutdown behavior are predictable before it supports build or media workloads.
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.