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
Fix: duplicated error message if a crash occurs (fixes #8964) #8965
Conversation
LGTM |
fc2abb0
to
95ccfde
Compare
LGTM |
@@ -44,11 +44,10 @@ process.once("uncaughtException", err => { | |||
if (typeof err.messageTemplate === "string" && err.messageTemplate.length > 0) { | |||
const template = lodash.template(fs.readFileSync(path.resolve(__dirname, `../messages/${err.messageTemplate}.txt`), "utf-8")); | |||
|
|||
console.log("\nOops! Something went wrong! :("); | |||
console.log(`\n${template(err.messageData || {})}`); | |||
console.error("\nOops! Something went wrong! :("); |
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 wonder if this might be considered as a breaking change? If somebody wrote an integration that listens for stdout they will get nothing in the case of the crash. But I think that's too much of an edge case.
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 suppose that's possible. Do you think it would be better to separate that into a different commit and schedule it for 5.0?
What is the purpose of this pull request? (put an "X" next to item)
[x] Bug fix (#8964)
What changes did you make? (Give an overview)
This updates the uncaught exception handler to avoid printing the error message twice. The error message is included in the stack, so it's not necessary to print the error message and the stack separately.
Is there anything you'd like reviewers to focus on?
Nothing in particular