[ruby] remove unnecessary background thread startup wait logic that interferes with forking #33805
Conversation
This file contains 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
apolcyn
added
lang/ruby
release notes: yes
grpc-checks
bot
added
per-call-memory/neutral
per-channel-memory/neutral
bloat/none
labels
|
Thanks, I'll test it Monday. |
feel free to merge if you are confident with the fix though. |
apolcyn
added a commit
to apolcyn/grpc
that referenced
this pull request
Jul 24, 2023
…nterferes with forking (grpc#33805) Alternative to grpc#33804 - this takes the approach in grpc#33804 (comment) Fix grpc#33802 cc @casperisfine
copybara-service
bot
added
the
imported
mario-vimal
pushed a commit
to mario-vimal/grpc
that referenced
this pull request
Jul 27, 2023
…nterferes with forking (grpc#33805) Alternative to grpc#33804 - this takes the approach in grpc#33804 (comment) Fix grpc#33802 cc @casperisfine
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Alternative to #33804 - this takes the approach in #33804 (comment)
Fix #33802
cc @casperisfine