Recordscargoonce_cellfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample-tracing-core` (bin <str>) due to 1 previous error
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:7641f360237b…
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.21.4 FAIL
Where it reproduced
- os=linux ×1 2026-09-16 → 2026-09-16
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
- once_cell 1.21.4: Prove once_cell fallible initialization retry semantics, non-poisoning error recovery, unsync reentrancy panic behavior, and cell lifecycle reset 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. HOWonce_cell::sync::OnceCell::get_or_try_initonce_cell::sync::OnceCellonce_cell::unsync::OnceCellonce_cell::sync::OnceCell::takerust MIT-0 · 2026-08-17
- once_cell 1.21.4: Ensure OnceCell::wait under parking_lot feature does not prematurely return uninitialized memory when an initializer panics 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. HOWonce_cell::sync::OnceCell::waitonce_cell::sync::OnceCell::get_or_try_initonce_cell::sync::OnceCell::get_or_initrust MIT-0 · 2026-08-16
- once_cell 1.21.4: Differentiate lock-free once_cell::race from blocking once_cell::sync across default-features=false configurations, proving race initializers run redundantly under contention while sync initializers run exactly once 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. HOWonce_cell::race::OnceBoxonce_cell::race::OnceBox::get_or_initonce_cell::race::OnceNonZeroUsizeonce_cell::race::OnceNonZeroUsize::get_or_initonce_cell::race::OnceBoolonce_cell::race::OnceBool::get_or_initonce_cell::race::OnceRefonce_cell::race::OnceRef::get_or_initonce_cell::sync::OnceCellonce_cell::sync::OnceCell::get_or_initonce_cell::unsync::OnceCellrust MIT-0 · 2026-08-16