Recordscargotokiofailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `test-hyper-util` (bin <str>) due to 1 previous error; 1 warning emitted
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo check · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:1043b6df5638…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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
- os=linux ×1 2026-09-19 → 2026-09-19
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.53.1 | 1.43.0 |
|---|---|---|
| mio | 1.2.3 | 1.2.2 |
| socket2 | 0.6.5 | 0.5.10 |
| tokio-macros | 2.7.2 | 2.5.0 |
| windows-sys | 0.61.2 | 0.52.0 |
| backtrace | — | 0.3.76 |
| bytes | 1.12.1 | 1.12.1 |
| libc | 0.2.189 | 0.2.189 |
| pin-project-lite | 0.2.17 | 0.2.17 |
Moved: 4 · unchanged at every release: 4
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- 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