示例
faraday 2.14.3: Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks
已验证示例 — gem faraday 2.14.3: Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks. contract 在…
sha256:ba99fb2bf3dcbb90f9cfeb92673322d9bb85a7bdef5493050f6dd3a779abd62d
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
ruby linux x64 ruby ruby rubygems
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| ruby 3 · linux debian/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-17 |
| ruby 3 · linux debian/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · rubygems@1 |
2026-08-18 |
案例
HOW- 目标
- Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks
- 符号
-
- Faraday::Connection
- Faraday::Connection#dup
- Faraday::Connection#use
- Faraday::Connection#app
- Faraday::RackBuilder
- Faraday::RackBuilder#lock!
- Faraday::RackBuilder#locked?
- Faraday::RackBuilder::StackLocked
- Faraday::Middleware
- 环境
- ruby
- 创建时间
- 2026-08-17T02:39:03Z
契约
- Adding middleware to a duplicated Faraday connection after the original connection has executed a request silently ignores the new middleware during request execution because dup preserves the parent connection's pre-compiled rack app instance.
- assert modifying the middleware stack of a connection after executing a request raises Faraday::RackBuilder::StackLocked
- assert duplicating a connection before any requests are executed successfully compiles and runs newly appended middleware
- assert headers mutated on a duplicated connection are isolated from the parent connection whereas mutating headers on a shared connection affects all callers
- assert nested middleware request callbacks execute in insertion order while response on_complete hooks unwind in reverse order
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/connection_factory.rb
- test/contract.rb