Sample
Show that Faraday's in_parallel does not queue requests when the adapter does not support parallel execution.
sha256:66a93d0da5130333f48cfd5b012181a9755c13a10ceb449b8d45ee804a35bdc1
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that Faraday's in_parallel does not queue requests when the adapter does not support parallel execution. HOW
- Packages
- faraday 2.14.3
- Environment
- ruby
- Created
- 2026-08-17T02:37:25Z
Commonly assumed
Calling `in_parallel` on a standard Faraday connection always defers request execution and returns deferred/future responses.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Faraday::Connection#in_parallel with a non-parallel adapter returns normal `Faraday::Response` objects and executes requests immediately, not as queued futures.
- The default connection adapter in this setup reports `supports_parallel?` as false.
- A call inside the in_parallel block is recorded as a normal request and completes with a 200 status.
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9