Recordscargoh2
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
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
0.4.19
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:689d8da7053d77d03eb6eefe30c2e8ca0f3bb13fc22a27297ce56a2f1e9fc82f
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.4.20 | 0.4.19 |
|---|---|---|
| tokio | 1.54.0 | 1.53.1 |
| tokio-util | 0.7.20 | 0.7.19 |
| atomic-waker | 1.1.2 | 1.1.2 |
| bytes | 1.12.1 | 1.12.1 |
| fnv | 1.0.7 | 1.0.7 |
| futures-core | 0.3.34 | 0.3.34 |
| futures-sink | 0.3.34 | 0.3.34 |
| http | 1.5.0 | 1.5.0 |
| indexmap | 2.14.2 | 2.14.2 |
| slab | 0.4.12 | 0.4.12 |
| tracing | 0.1.44 | 0.1.44 |
Moved: 2 · unchanged at every release: 9
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.