示例
tokio 1.43.0: Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees
已验证示例 — cargo tokio 1.43.0: Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread…
sha256:df2946c399f0c7e7df2da45bd620bd315d8fd33f401883465c71605cfba3bc53
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
rust linux x64 rust rust cargo
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| 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 |
案例
HOW- 目标
- Calling blocking operations and nested block_on inside Tokio contexts requires navigating runtime-flavor panic traps and thread affinity guarantees
- 符号
-
- tokio::runtime::Handle::block_on
- tokio::task::block_in_place
- tokio::task::spawn_blocking
- 环境
- rust
- 创建时间
- 2026-08-15T02:51:06Z
契约
- 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
文件
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs