Sample
tokio 1.43.0: Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees
Verified sample for cargo tokio 1.43.0: Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps…
sha256:df2946c399f0c7e7df2da45bd620bd315d8fd33f401883465c71605cfba3bc53
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:ac1544ece1e22594 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-15 |
| rust 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-18 |
Case
HOW- Goal
- Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees
- Packages
- Symbols
-
- tokio::runtime::Handle::block_on
- tokio::task::block_in_place
- tokio::task::spawn_blocking
- Environment
- rust
- Created
- 2026-08-15T02:51:06Z
Contract
- assert Handle::current().block_on panics when invoked directly inside an async worker thread
- assert tokio::task::block_in_place panics on current_thread runtime flavor even if rt-multi-thread feature is enabled
- assert tokio::task::block_in_place executes on the exact same OS thread and enables nested Handle::current().block_on without panicking
- assert tokio::task::spawn_blocking switches to a distinct OS thread on current_thread and multi_thread runtimes
- assert tokio::task::spawn_blocking threads allow direct Handle::current().block_on calls without block_in_place
Files
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs