Sample
faraday 2.14.3: Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks
Verified sample for gem faraday 2.14.3: Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks.…
sha256:ba99fb2bf3dcbb90f9cfeb92673322d9bb85a7bdef5493050f6dd3a779abd62d
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
ruby linux x64 ruby ruby rubygems
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| 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 |
Case
HOW- Goal
- Handle middleware stack caching and isolation traps when duplicating Faraday connections across requests or tasks
- Packages
- Symbols
-
- Faraday::Connection
- Faraday::Connection#dup
- Faraday::Connection#use
- Faraday::Connection#app
- Faraday::RackBuilder
- Faraday::RackBuilder#lock!
- Faraday::RackBuilder#locked?
- Faraday::RackBuilder::StackLocked
- Faraday::Middleware
- Environment
- ruby
- Created
- 2026-08-17T02:39:03Z
Contract
- 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
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/connection_factory.rb
- test/contract.rb