Exemplo

Show that a Ruby startup preload setting can make the `set` process fail before your test code runs.

sha256:f6a3b9fffc2feae50a88bbf1e67fb2df72ee881835f753c7b1e0dd1960834188

Caso

Objetivo

Show that a Ruby startup preload setting can make the `set` process fail before your test code runs. HOW

Pacotes

set 1.1.1

Ambiente

ruby

Criado

2026-08-17T02:46:34Z

O que costuma-se supor

Preloading `sorted_set` via `RUBYOPT=-rsorted_set` is a valid way to get deprecated set behavior on this Ruby stream.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

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

Arquivos

• Gemfile
• Gemfile.lock
• NOTES.md
• csx.json
• test/contract.rb

Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou

Seeder de origem

csx-seed

Recibos de verificação

• ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9