Recordscargoproc-macro2
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
Showing the environments with the most evidence.
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.0.107
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0d5a8e2ccc8650cb6b5b15c919d5bb10b9f10329752931e4b03800585a6b0656
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| unicode-ident | 1.0.24 | PASS All observations passed | contract passed | 81 project-days |
| unicode-ident | 1.0.25 | PASS All observations passed | builds observed | 15 project-days |
| unicode-ident | 1.0.26 | PASS All observations passed | contract passed | 110 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.