Recordscargoitoafailure issue
Failure signature
PROJECT_COMPILE exit 101 E0425 ×1
error[E0425]: cannot find function `write` in crate `itoa`
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo build · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:8a470a259e48…
itoa
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.
- 1.0.18 FAIL
Where it reproduced
- os=linux ×1 2026-09-14 → 2026-09-14
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- itoa 1.0.18: itoa::Buffer 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. HOWitoa::Buffer MIT-0 · 2026-09-14
- itoa 1.0.18: itoa 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. HOWitoa MIT-0 · 2026-09-14
- itoa 1.0.18 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. HOW MIT-0 · 2026-09-14