Recordscargoserdefailure issue
Failure signature
PROJECT_COMPILE exit 101 E0609 ×1
error[E0609]: no field `SINGLETON_NORMALIZER_NFC_V1` on type `MyProvider`
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-20 · Last seen: 2026-09-20
sha256:463107715912…
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.229 FAIL
Where it reproduced
- os=linux ×1 2026-09-20 → 2026-09-20
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
- serde 1.0.229: Flattening an Option<T> field with serde silently instantiates Some(T) with all None fields when input keys are completely missing instead of evaluating to None 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. HOWserde::Deserializerust MIT-0 · 2026-08-17
- serde 1.0.229: Serializing and deserializing standard reference-counted pointers Arc and Rc requires the opt-in rc Cargo feature flag on serde, which serializes transparently as the inner value but reconstructs independent allocations without preserving pointer identity on deserialization 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. HOWserde::Serializeserde::Deserializestd::sync::Arcstd::rc::Rcrust MIT-0 · 2026-08-16
- serde 1.0.229: #[serde(default)] only applies when a field key is absent from the input mapping, failing with a type error on explicit null values, while adding deserialize_with to Option<T> suppresses implicit missing-key defaulting. 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. HOWserde::Deserializeserde::de::Deserializerrust MIT-0 · 2026-08-16