Sample
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
Case
- Goal
- Show that a Ruby startup preload setting can make the `set` process fail before your test code runs. HOW
- Packages
- set 1.1.1
- Environment
- ruby
- Created
- 2026-08-17T02:46:34Z
Commonly assumed
Preloading `sorted_set` via `RUBYOPT=-rsorted_set` is a valid way to get deprecated set behavior on this Ruby stream.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
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.
Files
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9