Thread.report_on_exception default value is now true#5108
Merged
enebo merged 1 commit intojruby:ruby-2.5from Mar 26, 2018
Merged
Conversation
Unhandled exceptions terminating threads are shown on $stderr. For more information, please see feature #14143.
Member
|
are you sure about the warning message format? seems they agreed on smt different on the tracker ... |
Contributor
Author
|
@kares That's the message that I observed when tested MRI and also I read it in their source code. Please see below: |
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
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.
Hi folks,
This is another change targeting Ruby 2.5 [1]: Thread.report_on_exception default value is now true (feature 14143).
Thanks for your review and feedback.