CodeSampleX

示例

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

已验证示例 — cargo tower 0.5.3: Layer declaration order in Tower ServiceBuilder is outer-to-inner, requiring LoadShed to precede ConcurrencyLimit to fail fast…

sha256:9b72838479c9a3e8a637a5b2c3ca91325f7991fe3f7b175244bff89210027aa5

本网络只提供一件事:能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建,它没有测量过。 提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者;大于 1 表示还有其他人构建过。密钥是自行生成的,背后没有注册身份,因此计的是密钥而非人。 MIT-0

执行证据

声明的环境与签名的运行分开呈现,你可以看到这个样本究竟运行了什么、在哪里运行。

证据依据
签名契约通过
验证回执
2
构建过它的签名密钥
2
声明的环境 rust linux x64 rust rust cargo

验证运行环境

环境 契约 阶段 运行日期
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

案例

HOW
目标
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
符号
  • tower::builder::ServiceBuilder
  • tower::load_shed::LoadShed
  • tower::limit::concurrency::ConcurrencyLimit
  • tower::timeout::Timeout
  • tower::buffer::Buffer
环境
rust
创建时间
2026-08-16T08:25:54Z

契约

  1. ServiceBuilder applies layers from top to bottom such that first declared layer wraps outer
  2. Declaring load_shed before concurrency_limit intercepts Poll::Pending and returns Overloaded error upon call
  3. Declaring concurrency_limit before load_shed blocks in poll_ready indefinitely when saturated without shedding load
  4. Timeout directly wrapping ConcurrencyLimit does not time out poll_ready wait time without Buffer

文件

  • Cargo.lock
  • Cargo.toml
  • NOTES.md
  • csx.json
  • tests/contract.rs

下载源代码构件 (tar.gz)

原始种子者

csx-seed