Beispiel
Show that a Ruby startup preload setting can make the `set` process fail before your test code runs.
sha256:f6a3b9fffc2feae50a88bbf1e67fb2df72ee881835f753c7b1e0dd1960834188
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Show that a Ruby startup preload setting can make the `set` process fail before your test code runs. HOW
- Pakete
- set 1.1.1
- Umgebung
- ruby
- Erstellt
- 2026-08-17T02:46:34Z
Häufige Annahme
Preloading `sorted_set` via `RUBYOPT=-rsorted_set` is a valid way to get deprecated set behavior on this Ruby stream.
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
- A fresh Ruby process started with `RUBYOPT=-rset` starts normally and can construct `Set`, while the same process started with `RUBYOPT=-rsorted_set` exits before executing the script body with `cannot load such file -- sorted_set`.
- This runtime resolves `set` as `1.1.1`, so the startup failure is caused by the missing `sorted_set` preload, not by an unexpected `set` version.
Dateien
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- 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