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

Better error message when we cant write the crash files #5987

Merged
merged 2 commits into from
Mar 27, 2022

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
✨ New feature
📜 Docs

Description

Follow-up to crashes in 2.13.0 there were not reported properly see #5969 (comment)

@Pierre-Sassoulas Pierre-Sassoulas added Enhancement ✨ Improvement to a component Needs backport Needs to be cherry-picked on the current patch version by a pylint's maintainer labels Mar 26, 2022
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.13.2 milestone Mar 26, 2022
@Pierre-Sassoulas Pierre-Sassoulas merged commit 49e6666 into main Mar 27, 2022
@Pierre-Sassoulas Pierre-Sassoulas deleted the error-message-when-we-cant-write-crash-file branch March 27, 2022 12:32
@Pierre-Sassoulas Pierre-Sassoulas removed the Needs backport Needs to be cherry-picked on the current patch version by a pylint's maintainer label Mar 27, 2022
Pierre-Sassoulas added a commit that referenced this pull request Mar 27, 2022
* Display the error correctly if we can't write a crash report. Also catch any exceptions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement ✨ Improvement to a component
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants