Sample
tower-service 0.3.3: Show that tower-service behavior changed across the 0.2 to 0.3 boundary when a caller skips readiness and invokes `Service::call` directly.
Verified sample for cargo tower-service 0.3.3: Show that tower-service behavior changed across the 0.2 to 0.3 boundary when a caller skips readiness and…
sha256:5464f886e34a70d5aeb3876e92c1d40b6e1ce5892aae88a53b6c2ee75a10cb9f
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.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
rust linux x64 rust rust cargo
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| rust 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-16 |
| rust 1 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-18 |
Case
HOW- Goal
- Show that tower-service behavior changed across the 0.2 to 0.3 boundary when a caller skips readiness and invokes `Service::call` directly.
- Packages
- Symbols
-
- tower_service::Service
- Environment
- rust
- Created
- 2026-08-16T11:11:22Z
Contract
- assert!(call_without_poll_ready_panics())
- assert!(ready_then_call_succeeds())
Files
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs