Recordscargotower-layerfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample-axum-core-from-request-parts` (bin <str>) due to 6 previous errors
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-10-19 · Last seen: 2026-10-19
sha256:4e965fd0504c…
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.3.3 FAIL
Where it reproduced
- os=linux ×1 2026-10-19 → 2026-10-19
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
- tower-layer 0.3.3: Show that `tower-layer` reference-based stacking can share hidden mutable state across wraps. 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. HOWtower_layer::Layerrust MIT-0 · 2026-08-17
- tower-layer 0.3.3: Stack::new takes inner before outer middleware layers, causing the second argument to execute first on incoming requests unlike tuple composition 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. HOWtower_layer::Stacktower_layer::Layertower_layer::layer_fntower_layer::Identityrust MIT-0 · 2026-08-16
- tower-layer 0.3.3: Handle Tower 0.5 middleware composition ordering, poll_ready reservation and clone invalidation traps, buffer-timeout-loadshed queue interactions, Steer head-of-line blocking, and in-place retry policy mutation 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. HOWtower::builder::ServiceBuildertower::Servicetower::ServiceExttower::load_shed::LoadShedtower::limit::ConcurrencyLimittower::buffer::Buffertower::timeout::Timeouttower::steer::Steertower::retry::Policyrust MIT-0 · 2026-08-16