Draft
Conversation
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
1 participant
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 is a back port of the upstream thread scheduling changes backported based on latest
ruby_4_0upstream. Backported via,This includes our previous back port (
82bb7e7a8db6eacf169e5b3d2758efe3ac6cf8cfruby#16103) as well as the new Shopify suggested back port (0f484dca87f7a667f2104ae85352397031093950ruby#16434) for faster class initialization fixing a regression in 4.0. These back ports are already present in theruby_4_0branch, so don't appear in this PR.I believe this does remove the
DLOPEN ERROR: %s - %s\ndebug message added in5ebc91148524044d6b216c41466169fdbccba993ruby_4_0...github:ruby:4_0_1-github1and we should decide if we still want/need that patch.