Recordscargosynfailure issue
Failure signature
UNKNOWN exit 101 Evidence gap ×1
Compiling sample-wasm-bindgen v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.25s …
Evidence quality: complete · cargo · unclassified-diagnostic · outer cargo run · gap stage-unknown · First recorded: 2026-10-17 · Last seen: 2026-10-17
sha256:d5ef89c0ce65…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux ×1 2026-10-17 → 2026-10-17
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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 | 3.0.9 | 3.0.7 | 3.0.6 | 3.0.5 |
|---|---|---|---|---|
| unicode-ident | 1.0.27 | 1.0.26 | 1.0.25 | 1.0.25 |
| proc-macro2 | 1.0.107 | 1.0.107 | 1.0.107 | 1.0.107 |
| quote | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 |
Moved: 1 · unchanged at every release: 2
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.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.