示例
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
案例
- 目标
- Show that a Ruby startup preload setting can make the `set` process fail before your test code runs. HOW
- 包
- set 1.1.1
- 环境
- ruby
- 创建时间
- 2026-08-17T02:46:34Z
常见的想当然
Preloading `sorted_set` via `RUBYOPT=-rsorted_set` is a valid way to get deprecated set behavior on this Ruby stream.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- 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.
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9