Records/cargo/serde_json/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 1.0.151 FAIL
• 1.0.150 PASS 1 passing observations
• 1.0.149 FAIL

Where it reproduced

• executionContext=rust · os=linux · runtime=rust@1 ×2 2026-09-08 → 2026-09-08

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last failing release 1.0.149 → first passing release 1.0.150

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last passing release 1.0.150 → first failing release 1.0.151

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 0 · unchanged at every release: 5

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No resolved dependency tree for 1.0.150 or for 1.0.149, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• serde_json 1.0.151: Configure request payload size limits in axum using DefaultBodyLimit to prevent automatic 413 Payload Too Large rejections on buffering extractors (Bytes, String, Json) at the default 2MB boundary, override limits per route or sub-router, and stream unbuffered raw requests without limits Built ? 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. HOWaxum::extract::DefaultBodyLimitaxum::extract::DefaultBodyLimit::maxaxum::extract::DefaultBodyLimit::disableaxum::extract::Jsonaxum::extract::Requestaxum::body::Bytesaxum::Router::routeaxum::Router::layeraxum::Router::nestrust MIT-0 · 2026-08-16
• serde_json 1.0.151: 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 Built ? 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_json 1.0.151: #[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. Built ? 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
• serde_json 1.0.149: Parsing scientific notation numbers with serde_json arbitrary_precision normalizes positive and uppercase exponents to explicit lowercase e+ formatting matching zmij float serialization starting in 1.0.149 Built ? 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_json::Numberserde_json::from_strserde_json::to_stringserde_json::Valuerust MIT-0 · 2026-08-16