Sample
Prove that Faraday does not close caller-owned request streams after a completed POST.
sha256:120b78f41cb0cacae1b41bc79e9fdf64f352cb794bd70e368b81ef4dedd6a0ed
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that Faraday does not close caller-owned request streams after a completed POST. HOW
- Packages
- faraday 2.14.3 faraday-net_http 3.4.4
- Environment
- ruby
- Created
- 2026-08-17T02:40:08Z
Commonly assumed
A well-formed Faraday POST using an IO request body is expected to close that IO for the caller automatically.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Faraday returns normally from a POST with an IO request body while leaving the caller's stream open.
- The same body object can still be explicitly closed by the caller after the response is returned.
- Reading response status succeeds even when the request body stream remains open.
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