Recordscargoaxumfailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-08 · Last seen: 2026-09-08
axum::Json axum::Router::layer axum::Router::nest axum::Router::route axum::Router::route_layer axum::Router::with_state axum::body::Body axum::body::Bytes axum::debug_handler axum::extract::DefaultBodyLimit axum::extract::DefaultBodyLimit::disable axum::extract::DefaultBodyLimit::max axum::extract::Extension axum::extract::Json axum::extract::Path axum::extract::Query axum::extract::Request axum::extract::State axum::middleware::Next axum::middleware::from_fn axum::middleware::from_fn_with_state http_body_util::BodyExt::collect tower::ServiceExt::oneshot
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.
- 0.8.9 FAIL
Where it reproduced
- executionContext=rust · os=linux · runtime=rust@1 ×1 2026-09-08 → 2026-09-08
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- axum 0.8.9: Handle silent breaking changes in axum 0.8 OptionalFromRequest and OptionalFromRequestParts extractors where malformed Path, invalid Json, and tuple arity mismatches reject with 400, 415, 422, or 500 instead of returning 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. HOWaxum::extract::Pathaxum::extract::OptionalFromRequestPartsaxum::extract::OptionalFromRequestaxum::Jsonaxum::Router::routetower::ServiceExt::oneshotrust MIT-0 · 2026-08-16
- axum 0.8.9: Protect axum routes with stateful middleware using from_fn_with_state, isolate route_layer from 404 fallbacks, and manage bottom-to-top layer execution order 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::middleware::from_fnaxum::middleware::from_fn_with_stateaxum::middleware::Nextaxum::Router::route_layeraxum::Router::layeraxum::extract::Extensionaxum::extract::Stateaxum::extract::Requestrust MIT-0 · 2026-08-16
- axum 0.8.9: Merge a CONNECT route handler into an axum MethodRouter without it overwriting options or returning 405 Method Not Allowed 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::routing::MethodRouter::mergeaxum::routing::connectrust MIT-0 · 2026-08-16