Stop Bundler from using load to launch an executable in-process in bundle exec
#650
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
…ndle exec. See rubygems/bundler#6090. This stops SignalException from being handled by Bundler when using `bundle exec` and instead by Ruby. As of Puma 3.10.0, Puma changed the SIGTERM hanlding to be passed back to the parent process, `bundle exec` in this case.
|
Fixed in bundler 2.0.2 ? Either way i've not seen any reports about this in a long time and this PR is really old. Going to close, let me know if you disagree. |
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.
See rubygems/bundler#6090. This stops
SignalException from being handled by Bundler when using
bundle execand instead by Ruby. As of Puma 3.10.0, Puma changed the SIGTERM
hanlding to be passed back to the parent process,
bundle execin thiscase.