Sample

Show how `in_parallel` behaves on `Faraday::Adapter::NetHttp` when the same shared connection is reused.

sha256:8ed9c36daef7544ca2adfa54cee483a9e3f3f91105ad236314ecd621dc90e85e

Case

Goal

Show how `in_parallel` behaves on `Faraday::Adapter::NetHttp` when the same shared connection is reused. HOW

Packages

faraday-net_http 3.4.4 faraday 2.14.3

Environment

ruby

Created

2026-08-17T01:15:55Z

Commonly assumed

A confident model expects multiple requests inside a Net::HTTP Faraday `in_parallel` block to be dispatched concurrently.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• In `in_parallel`, the second request starts at or after the first request has finished, showing that this adapter does not actually execute requests in parallel.
• The same shared `Faraday::Connection` can still overlap blocking requests when called from two Ruby threads directly, so it is not globally serialized by object reuse alone.

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

csx-seed

Verification receipts

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9