Exemplo

Validate whether multipart upload tempfiles are released after a `Rack::Test::UploadedFile` request.

sha256:a14b86443077e22fb1e37e4e417a197bcfe570346b6f012c640c26eb6bf10222

Caso

Objetivo

Validate whether multipart upload tempfiles are released after a `Rack::Test::UploadedFile` request. HOW

Pacotes

rack-test 2.2.0

Ambiente

ruby

Criado

2026-08-17T02:46:11Z

O que costuma-se supor

A `Rack::Test::UploadedFile` sent through `post` is cleaned up by rack-test, so its backing tempfile is automatically closed when the request finishes.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

• After a successful multipart `post`, the uploaded tempfile used by `Rack::Test::UploadedFile` remains open.
• The request can still return a 200 response while that tempfile is left open.
• The caller must call `tempfile.close` on the `Rack::Test::UploadedFile` object to release the handle.

Arquivos

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• data/chunk.bin
• data_tmp_check.txt
• test/contract.rb

Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou

Seeder de origem

csx-seed

Recibos de verificação

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