Sample

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

sha256:a14b86443077e22fb1e37e4e417a197bcfe570346b6f012c640c26eb6bf10222

Case

Goal

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

Packages

rack-test 2.2.0

Environment

ruby

Created

2026-08-17T02:46:11Z

Commonly assumed

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

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

Contract

• 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.

Files

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• data/chunk.bin
• data_tmp_check.txt
• 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