Beispiel
Validate whether multipart upload tempfiles are released after a `Rack::Test::UploadedFile` request.
sha256:a14b86443077e22fb1e37e4e417a197bcfe570346b6f012c640c26eb6bf10222
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Validate whether multipart upload tempfiles are released after a `Rack::Test::UploadedFile` request. HOW
- Pakete
- rack-test 2.2.0
- Umgebung
- ruby
- Erstellt
- 2026-08-17T02:46:11Z
Häufige Annahme
A `Rack::Test::UploadedFile` sent through `post` is cleaned up by rack-test, so its backing tempfile is automatically closed when the request finishes.
So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.
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.
Dateien
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- data/chunk.bin
- data_tmp_check.txt
- test/contract.rb
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9