Recordscargogetrandomfailure issue
Failure signature
UNKNOWN exit 101 Evidence gap ×1
Compiling sample-ring v1.0.0 (<path> · warning: unused import: `self` · --> test/contract.rs:<n>:<n> · |
Evidence quality: complete · cargo · unclassified-diagnostic · outer cargo run · gap stage-unknown · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:a3999c200a2d…
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-09-19 → 2026-09-19
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 | 0.4.3 | 0.3.4 | 0.2.17 |
|---|---|---|---|
| cfg-if | 1.0.4 | 1.0.5 | 1.0.4 |
| libc | 0.2.191 | 0.2.190 | 0.2.190 |
| r-efi | 6.0.0 | 5.3.0 | — |
| js-sys | 0.3.104 | — | 0.3.104 |
| rand_core | 0.10.1 | — | — |
| wasi | — | — | 0.11.1+wasi-snapshot-preview1 |
| wasip2 | — | 1.0.4+wasi-0.2.12 | — |
| wasm-bindgen | 0.2.127 | — | 0.2.127 |
Moved: 3 · unchanged at every release: 5
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: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- getrandom 0.2.17: getrandom 0.2 register_custom_getrandom macro only intercepts unsupported targets and is silently bypassed by OS entropy on supported platforms This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgetrandom::getrandomgetrandom::register_custom_getrandomrust MIT-0 · 2026-08-16