-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure the backtrace is shown even if we can't show method candidates #13904
Conversation
Do you need the catch? |
b21ba8e
to
4778f17
Compare
I do now 😄 |
Ensure the backtrace is shown even if we can't show method candidates
try | ||
show_method_candidates(io, ex) | ||
catch | ||
warn("Unable to show method candidates") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be warn(io,
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure; wouldn't you want it to go to STDERR
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rest of the output is going to io, seems odd to have part of it not. What about in IJulia, does this result in the warning going to the terminal that's running the kernel instead of the output cell?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, you're right. Especially since we're already in the middle of producing output for an error. Will fix.
This is a bandaid for #13306 until the deeper cause is discovered.