CodeSampleX

Recordscargotokio1.53.1

Change the conditions
Fixed
OSubuntu glibc
Filter Package version1.53.1 Symbolwhole package Architecturex64 Package managercargo 1 libcglibc Clear filters

Current conditions

tokio @1.53.1ubuntu glibc · x64 · cargo 1

package-level total, not an API

12 of 20 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (8)

Project observations
12 / 20
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-20
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 3

First observed break

1.53.1

linux · rust@1 · executionContext=rust

2 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
mio 1.2.2 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
mio 1.2.3 CANDIDATE Correlated change; unproven combination builds observed 2 project-days
socket2 0.6.5 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
tokio-macros 2.7.2 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
windows-sys 0.61.2 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
bytes 1.12.1 PASS All observations passed contract passed 5 project-days
libc 0.2.189 PASS All observations passed contract passed 8 project-days
pin-project-lite 0.2.17 PASS All observations passed contract passed 20 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.

Library1.53.11.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.

Recent failure clusters