Recordscargoinoutfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample-cipher` (bin <str>) due to 2 previous errors
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-11-09 · Last seen: 2026-11-09
sha256:165d3075106a…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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-11-09 → 2026-11-09
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.2.6 | 0.2.5 |
|---|---|---|
| hybrid-array | 0.4.15 | 0.4.15 |
Moved: 0 · unchanged at every release: 1
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.