Broken · simplified example
owner_a.respond()
owner_b.respond()
on_any_activity:
cancel_fallback()Two owners can overlap, and a control event can cancel the only recovery path.
DentSignal engineering case study · Async reliability
Two components tried to answer once.
Competing response paths could duplicate output, stop recovery before playable bytes arrived, or leave later work waiting. The repair gave one path ownership and made cancellation depend on real output.
- Area
- Async state, streaming events, cancellation
- Evidence
- Historical PR-reported validation
- Boundary
- Controlled tests, not latency promise
Plain English
One request needs one owner.
- What broke
Two response paths could act on the same turn, while control activity was mistaken for sound a person could actually hear.
- What changed
One path became the owner, queued speculative work was cleared, and recovery stopped only after playable output arrived.
- Why it matters
Explicit ownership prevents duplicate answers. A 2.5-second fallback also bounds silence when the primary path produces nothing.
Simplified repair
Cancel recovery only for usable output.
Fixed · simplified example
response_owner = primary
on_playable_output:
cancel_fallback()
await fallback_after(2.5)One owner responds; only audible output cancels the bounded fallback.
Illustration only — not copied from private source.
How it was checked
Historical PR-reported validation
The cited history reports 304, 306, and 310 focused or broader tests across the successive ownership, cancellation, and fallback corrections, plus formatting and diff checks.