Recordscargotokio-util0.7.19
Change the conditions
Current conditions
tokio-util @0.7.19alpine musl · x64 · rust 1 · cargo · rust
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.7.19
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:689d8da7053d77d03eb6eefe30c2e8ca0f3bb13fc22a27297ce56a2f1e9fc82f
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| libc | 0.2.189 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| tokio | 1.53.1 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| bytes | 1.12.1 | PASS All observations passed | contract passed | 3 project-days |
| futures-core | 0.3.34 | PASS All observations passed | contract passed | 3 project-days |
| futures-sink | 0.3.34 | PASS All observations passed | contract passed | 3 project-days |
| pin-project-lite | 0.2.17 | PASS All observations passed | contract passed | 3 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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 | 0.7.20 | 0.7.19 |
|---|---|---|
| libc | 0.2.191 | 0.2.189 |
| tokio | 1.54.0 | 1.53.1 |
| bytes | 1.12.1 | 1.12.1 |
| futures-core | 0.3.34 | 0.3.34 |
| futures-sink | 0.3.34 | 0.3.34 |
| pin-project-lite | 0.2.17 | 0.2.17 |
Moved: 2 · 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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 E0599 ×1 0.7.19 os=linux sha256:689d8da7053d…error[E0599]: no method named `http1_only` found for mutable reference `&mut hyper_util::client::legacy::Builder` in the current scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19
-
observed PROJECT_COMPILE exit 101 ×1 0.7.19 os=linux sha256:a67fd218023f…error: could not compile `test-hyper-util` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-19 · Last seen: 2026-09-19