Skip to content
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

Merged
merged 1 commit into from
Nov 8, 2015

Conversation

timholy
Copy link
Sponsor Member

@timholy timholy commented Nov 6, 2015

This is a bandaid for #13306 until the deeper cause is discovered.

@yuyichao
Copy link
Contributor

yuyichao commented Nov 6, 2015

Do you need the catch?

@timholy
Copy link
Sponsor Member Author

timholy commented Nov 8, 2015

I do now 😄

timholy added a commit that referenced this pull request Nov 8, 2015
Ensure the backtrace is shown even if we can't show method candidates
@timholy timholy merged commit 3f74f34 into master Nov 8, 2015
@timholy timholy deleted the teh/methoderrors branch November 8, 2015 13:43
try
show_method_candidates(io, ex)
catch
warn("Unable to show method candidates")
Copy link
Contributor

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, ?

Copy link
Sponsor Member Author

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?

Copy link
Contributor

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?

Copy link
Sponsor Member Author

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.

@tkelman tkelman mentioned this pull request Nov 9, 2015
timholy added a commit that referenced this pull request Nov 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants