Recordscargoconst-oidfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0271 ×1
error[E0271]: type mismatch resolving `<&[{integer}; 7] as IntoIterator>::Item == u32`
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-11-04 · Last seen: 2026-11-04
sha256:bbd7ada8b7cc…
const_oid::Error const_oid::ObjectIdentifier
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.9.6 FAIL
Where it reproduced
- os=linux ×1 2026-11-04 → 2026-11-04
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
- const-oid 0.9.6: const_oid::db 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. HOWconst_oid::db MIT-0 · 2026-11-04
- const-oid 0.9.6: const_oid::ObjectIdentifier 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. HOWconst_oid::ObjectIdentifier MIT-0 · 2026-11-04
- const-oid 0.9.6: const_oid::AssociatedOid 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. HOWconst_oid::AssociatedOid MIT-0 · 2026-11-04