Sample
Enforce explicit pre-setup reloading opt-in and handle ReloadingDisabledError in Zeitwerk 2 autoloader lifecycle
sha256:fde2bfda11c8653139007ab202730c660140bc58e0c5f2d5334a8bd52f56eb70
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Enforce explicit pre-setup reloading opt-in and handle ReloadingDisabledError in Zeitwerk 2 autoloader lifecycle HOW
- Packages
- zeitwerk 2.8.3
- Environment
- ruby
- Created
- 2026-08-17T01:23:49Z
Commonly assumed
Calling loader.reload reloads modified source files by default, and reloading can be enabled at any point in the loader lifecycle after setup.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling loader.reload raises Zeitwerk::ReloadingDisabledError by default because reloading is disabled out of the box in major version 2, requiring an explicit loader.enable_reloading call before setup.
- assert loader.enable_reloading called after loader.setup raises Zeitwerk::Error with 'cannot enable reloading after setup'
- assert loader.reloading_enabled? returns false by default and true only after calling loader.enable_reloading before setup
- assert loader.reload with reloading enabled successfully unloads and reloads modified constants from disk
- assert failing to define the expected constant in a managed file raises Zeitwerk::NameError rather than standard NameError
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