Recordscargowriteablefailure issue
Failure signature
PROJECT_COMPILE exit 101 E0432 ×1
error[E0432]: unresolved import `icu_locale_core::subtag`
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:09d871767659…
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.
- 0.6.4 FAIL
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.
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
- writeable 0.6.4: writeable 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. HOWwriteable MIT-0 · 2026-09-20
- writeable 0.6.4: writeable::LengthHint, writeable::TryWriteable, writeable::Writeable 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. HOWwriteable::LengthHintwriteable::TryWriteablewriteable::Writeablewriteable::assert_writeable_eqwriteable::cmp_strwriteable::impl_display_with_writeable MIT-0 · 2026-09-18