Sample
Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees
sha256:df2946c399f0c7e7df2da45bd620bd315d8fd33f401883465c71605cfba3bc53
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees HOW
- Packages
- tokio 1.43.0
- 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
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- rust 1 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · cargo@1 · 2026-08-15 · ed25519:ac1544ece1e22594