fix(runtime): allow prefork loading before runtime init - #164
Merged
Conversation
0x676e67
changed the title
ZilvinasKucinskas
approved these changes
Aug 16, 2026
ZilvinasKucinskas
left a comment
ZilvinasKucinskas
left a comment
Contributor
There was a problem hiding this comment.
Tested the prefork behavior across Puma preload! and Minitest parallel workers. Everything looks good. Approved ✅
0x676e67
force-pushed
the
fix/allow-prefork-before-runtime-init
branch
from
August 16, 2026 22:35
29d0332 to
072994d
Compare
0x676e67
marked this pull request as ready for review
August 16, 2026 23:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change keeps runtime initialization lazy and moves the ownership check into the runtime entry point. Loading wreq-ruby before fork is supported again, so each worker can initialize its own runtime on first use. Native clients, cookie jars, body senders, responses, and an already initialized parent runtime remain process-local and still raise
Wreq::ForkErrorwhen inherited. The fork behavior and application guidance are documented alongside the Ruby APIs.