CodeSampleX

Recordscargotracing

there is a sample for this release and API (2)

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version0.1.44 Symbolwhole package
Filter Runtimerust 1 Architecturex64 Execution contextrust Clear filters
OS × Package manager
1○ 12026-11-17
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

Observed problems 1 · Unknown 1 · Steady 5

First observed break

0.1.44

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:689d8da7053d77d03eb6eefe30c2e8ca0f3bb13fc22a27297ce56a2f1e9fc82f

Library Version Health Measured there Projects
log 0.4.33 UNKNOWN No linked outcome measured nothing measured 4 project-days
log 0.4.34 PASS All observations passed contract passed 1 project-day
log 0.4.35 PASS All observations passed contract passed 7 project-days
pin-project-lite 0.2.17 PASS All observations passed contract passed 28 project-days
tracing-attributes 0.1.31 PASS All observations passed contract passed 4 project-days
tracing-core 0.1.36 PASS All observations passed contract passed 25 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.

Moved: 0 · 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.