Recordscargotokio
no sample at this coordinate yet
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
The cube reads the newest 6 versions and the first 10 symbols of each, so an empty cell here can mean "outside that window" rather than "never measured".
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.54.1
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:b81e23804da66669716e446549b14b14f0be1ade903503325d8c3ac34143c4e9
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| libc | 0.2.191 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| mio | 1.2.5 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| socket2 | 0.6.5 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| tokio-macros | 2.7.2 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| windows-sys | 0.61.2 | CANDIDATE Correlated change; unproven combination | 8 project-days | |
| pin-project-lite | 0.2.17 | UNKNOWN No linked outcome measured | 27 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 | 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.