Recordscargotokiofailure issue
Failure signature
PROJECT_TEST Evidence gap ×2
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-08 · Last seen: 2026-09-08
tokio::runtime::Builder tokio::runtime::Builder::enable_all tokio::runtime::Builder::enable_io tokio::runtime::Builder::enable_time tokio::runtime::Builder::worker_threads tokio::time::advance tokio::time::pause
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=rust · os=linux · runtime=rust@1 ×2 2026-09-08 → 2026-09-08
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 1.53.1 → first passing release 1.54.0
What differs across the boundary
- libc 0.2.191 → 0.2.189 hypothesis
- mio 1.2.4 → 1.2.2, 1.2.3 hypothesis
- tokio-macros — → 2.7.2 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 1.54.1 | 1.54.0 | 1.53.1 | 1.43.0 |
|---|---|---|---|---|
| libc | 0.2.191 | 0.2.191 | 0.2.189 | 0.2.189 |
| mio | 1.2.5 | 1.2.4 | 1.2.3 | 1.2.2 |
| socket2 | 0.6.5 | 0.6.5 | 0.6.5 | 0.5.10 |
| tokio-macros | 2.7.2 | — | 2.7.2 | 2.5.0 |
| windows-sys | 0.61.2 | 0.61.2 | 0.61.2 | 0.52.0 |
| backtrace | — | — | — | 0.3.76 |
| bytes | — | 1.12.1 | 1.12.1 | 1.12.1 |
| pin-project-lite | 0.2.17 | 0.2.17 | 0.2.17 | 0.2.17 |
Moved: 5 · unchanged at every release: 3
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tokio 1.53.1: Multiple notify_one calls on Tokio Notify store at most one permit when no waiters are present, while notify_waiters stores zero permits and wakes all registered waiters simultaneously This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtokio::sync::Notify::notify_onetokio::sync::Notify::notifiedtokio::sync::Notify::notify_waitersrust MIT-0 · 2026-08-17
- tokio 1.53.1: Distinguish reqwest Policy::none from Policy::limited(0), and inspect the initial URL through RedirectAttempt::previous in a custom redirect policy This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWreqwest::redirect::Policy::nonereqwest::redirect::Policy::limitedreqwest::redirect::Policy::customreqwest::redirect::Attempt::previousreqwest::Error::is_redirectrust MIT-0 · 2026-08-17
- tokio 1.53.1: Handle Tower 0.5 middleware composition ordering, poll_ready reservation and clone invalidation traps, buffer-timeout-loadshed queue interactions, Steer head-of-line blocking, and in-place retry policy mutation This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtower::builder::ServiceBuildertower::Servicetower::ServiceExttower::load_shed::LoadShedtower::limit::ConcurrencyLimittower::buffer::Buffertower::timeout::Timeouttower::steer::Steertower::retry::Policyrust MIT-0 · 2026-08-16
- tokio 1.43.0: Tokio Runtime::Builder disables time and IO drivers by default, time::pause requires current_thread runtime, and TOKIO_WORKER_THREADS=0 panics multi-thread builds This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtokio::runtime::Buildertokio::runtime::Builder::enable_timetokio::runtime::Builder::enable_iotokio::runtime::Builder::enable_alltokio::runtime::Builder::worker_threadstokio::time::pausetokio::time::advancerust MIT-0 · 2026-08-16
- tokio 1.43.0: Tokio watch channel change tracking requires borrow_and_update rather than borrow to acknowledge versions, send unconditionally wakes receivers even for identical values, and subscribe resets to latest version unlike clone This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtokio::sync::watch::channeltokio::sync::watch::Receiver::borrowtokio::sync::watch::Receiver::borrow_and_updatetokio::sync::watch::Receiver::has_changedtokio::sync::watch::Sender::sendtokio::sync::watch::Sender::send_if_modifiedtokio::sync::watch::Sender::subscriberust MIT-0 · 2026-08-16
- tokio 1.43.0: Tokio broadcast channels require navigating zero-receiver SendError drops, RecvError::Lagged stream recovery without premature loop termination, and late subscription history exclusion This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWtokio::sync::broadcast::channeltokio::sync::broadcast::Sender::sendtokio::sync::broadcast::Sender::subscribetokio::sync::broadcast::Receiver::recvtokio::sync::broadcast::Receiver::resubscriberust MIT-0 · 2026-08-16