Recordscargowindows-link0.2.1
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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.
Environment detail
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| unknown · Rust · cargo · linux glibc
Observations: PROJECT_COMPILE 3✓ 3✕ · PROJECT_PROCESS 4✓ — Usage: USED 2✓
|
ELEVATED FAILURE | 10 +2 | 0 | 70% | 1 | 2026-09-16 |
| rust 1 · Rust · cargo · linux musl · docker
Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 2✓ — Verified: CONTRACT 1✓
|
LOW | 4 +2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 101 ×1 0.2.1 os=linux windows_link::link sha256:20975e9182f9…error: could not compile `test_link` (bin <str>) due to 2 previous errors; 1 warning emittedrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 E0428 ×1 0.2.1 os=linux windows_link::link sha256:dc6199fb788f…error[E0428]: the name `custom_add` is defined multiple timesrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
-
observed PROJECT_COMPILE exit 101 ×1 0.2.1 os=linux windows_link::link sha256:f9563a1dbf38…error: could not compile `test_link` (bin <str>) due to 1 previous errorrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15
Symbols
- windows_link::link 1 1 of 1 runs passed