[release-1.9] Avoid usage of jl_error() in check_cmdline()#49486
Merged
staticfloat merged 1 commit intobackports-release-1.9from Apr 24, 2023
Merged
[release-1.9] Avoid usage of jl_error() in check_cmdline()#49486staticfloat merged 1 commit intobackports-release-1.9from
jl_error() in check_cmdline()#49486staticfloat merged 1 commit intobackports-release-1.9from
Conversation
staticfloat
changed the title
jl_error() in check_cmdline()jl_error() in check_cmdline()
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 the same as #45765 where we use
jl_error()too early to get backtraces, but too late to fail the supposed guardifstatement that should prevent us from trying to take a backtrace. X-ref: #45847(cherry picked from commit fa21589)