Ejemplo
Show how `in_parallel` behaves on `Faraday::Adapter::NetHttp` when the same shared connection is reused.
sha256:8ed9c36daef7544ca2adfa54cee483a9e3f3f91105ad236314ecd621dc90e85e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Show how `in_parallel` behaves on `Faraday::Adapter::NetHttp` when the same shared connection is reused. HOW
- Paquetes
- faraday-net_http 3.4.4 faraday 2.14.3
- Entorno
- ruby
- Creado
- 2026-08-17T01:15:55Z
Lo que suele suponerse
A confident model expects multiple requests inside a Net::HTTP Faraday `in_parallel` block to be dispatched concurrently.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- 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.
Archivos
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9