Recordscargotowerfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0599 ×1
error[E0599]: no method named `method_not_allowed_fallback` found for struct `MethodRouter<S, E>` in the current scope
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-11-17 · Last seen: 2026-11-17
sha256:4e616c2835f6…
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.
Where it reproduced
- os=linux ×1 2026-11-17 → 2026-11-17
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.
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.
| Library | 0.5.3 | 0.4.13 |
|---|---|---|
| futures-core | 0.3.34 | 0.3.34 |
| futures-util | 0.3.34 | 0.3.34 |
| pin-project | — | 1.1.13 |
| pin-project-lite | 0.2.17 | 0.2.17 |
| sync_wrapper | 1.0.2 | — |
| tokio | 1.53.1 | — |
| tokio-util | 0.7.19 | — |
| tower-layer | 0.3.3 | 0.3.3 |
| tower-service | 0.3.3 | 0.3.3 |
| tracing | 0.1.44 | 0.1.44 |
Moved: 0 · unchanged at every release: 10
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- tower 0.5.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
- tower 0.5.3: Layer declaration order in Tower ServiceBuilder is outer-to-inner, requiring LoadShed to precede ConcurrencyLimit to fail fast with Overloaded instead of hanging indefinitely in poll_ready 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::load_shed::LoadShedtower::limit::concurrency::ConcurrencyLimittower::timeout::Timeouttower::buffer::Bufferrust MIT-0 · 2026-08-16
- tower 0.5.3: Enforce Tower Service backpressure by pairing every call with a prior poll_ready, isolating Buffer permits from clones, and maintaining top-to-bottom ServiceBuilder layer ordering 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::Servicetower::ServiceExttower::buffer::Buffertower::limit::ConcurrencyLimittower::ServiceBuilderrust MIT-0 · 2026-08-16