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

Notify client on all dmypy crashes #7593

Merged
merged 1 commit into from Oct 1, 2019

Conversation

@msullivan
Copy link
Collaborator

msullivan commented Oct 1, 2019

This is done by setting the raise_exceptions option, which will cause
the exception to continue to be propagated.
Closes #4804.

Tested by introducing a crash in the parser and verifying the message
came through.

This is done by setting the raise_exceptions option, which will cause
the exception to continue to be propagated.
Closes #4804.

Tested by introducing a crash in the parser and verifying the message
came through.
@msullivan msullivan requested review from Michael0x2a and ilevkivskyi Oct 1, 2019
Copy link
Member

gvanrossum left a comment

Yeah!

@msullivan msullivan merged commit 583b99e into master Oct 1, 2019
0 of 3 checks passed
0 of 3 checks passed
continuous-integration/appveyor/branch Waiting for AppVeyor build to complete
Details
continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
@msullivan msullivan deleted the dmypy-crash branch Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.