Ejemplo

Handle IO request streaming, socket persistence, and response streams in faraday-net_http without unhandled ArgumentError exceptions or open stream leaks

sha256:ea9a12850f8c6125266e38da58c01e8daff93cdf5fd081a34b489c4f9d1732d6

Caso

Objetivo

Handle IO request streaming, socket persistence, and response streams in faraday-net_http without unhandled ArgumentError exceptions or open stream leaks HOW

Paquetes

faraday-net_http 3.4.4

Entorno

ruby

Creado

2026-08-17T02:42:06Z

Lo que suele suponerse

Passing an IO object as a request body automatically streams the payload without explicit transfer headers and closes the stream on completion, while Faraday::Connection retains persistent TCP sockets across calls.

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

• Passing an IO stream as a request body without an explicit Content-Length or chunked Transfer-Encoding header raises an ArgumentError, and even after successful transfer, NetHttp leaves the caller's IO stream open at EOF.
• Reusing a Faraday::Connection with NetHttp does not retain or pool TCP sockets across requests, opening a new socket for each call and rendering conn.close an effective no-op.
• Streaming a response using req.options.on_data delivers chunks during transmission but leaves response.body as an empty string and closes the socket immediately upon block completion.
• Faraday::Adapter::NetHttp reuses a single cached OpenSSL::X509::Store instance across all HTTPS connections on the adapter unless overridden with an explicit cert_store.

Archivos

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• lib/resource_helper.rb
• test/contract.rb

Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato

Seeder de origen

csx-seed

Recibos de verificación

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