Runtime bundled-library drift
Ruby 3.4 drb default gem bundled gem removed default gems
A health or remote-console feature fails only in production after upgrading the base image.
Agent Quick Fix
Repair against the current Ruby 3.4 contract, then keep the change narrow and source-backed.
Product: Ruby 3.4
Current-contract area: `drb` missing in a job-worker diagnostic path
Likely root cause: A health or remote-console feature fails only in production after upgrading the base image.
Repair direction: Verifier checks an explicit dependency or supported replacement and a clean install.Symptom
A health or remote-console feature fails only in production after upgrading the base image.
Why This Happens
A library was historically part of the default runtime install but is now only bundled/optional, so project dependency files may not mention it.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Ruby 3.4 drb default gem bundled gem removed default gems
site:ruby-lang.org Ruby 3.4 default gems drb
Ruby 3.4.0 release drb bundled gems
https://docs.ruby-lang.org/en/3.4/NEWS_md.html
'drb' in https://docs.ruby-lang.org/en/3.4/NEWS_md.html