-
Notifications
You must be signed in to change notification settings - Fork 212
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
feat(controller): louder UnhandledPromiseRejection log #7547
Conversation
@@ -75,7 +75,7 @@ function makeConsole(tagOrTagCreator) { | |||
function unhandledRejectionHandler(e, pr) { | |||
// Don't trigger sensitive hosts (like AVA). | |||
pr.catch(() => {}); | |||
console.error('UnhandledPromiseRejectionWarning:', e); | |||
console.error('🚨 UnhandledPromiseRejection:', e); |
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.
or maybe 📣 since it's not necessarily a problem.
alternately we can treat all failures as a problem and have an explicit catch for "expected to never happen" or "ignore failure"
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.
🤞
@@ -75,7 +75,7 @@ function makeConsole(tagOrTagCreator) { | |||
function unhandledRejectionHandler(e, pr) { | |||
// Don't trigger sensitive hosts (like AVA). | |||
pr.catch(() => {}); | |||
console.error('UnhandledPromiseRejectionWarning:', e); | |||
console.error('🚨 UnhandledPromiseRejection:', e); |
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.
🤞
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.
LGTM
5059ad9
to
cd67304
Compare
Description
On many occasion debugging the
UnhandledPromiseRejectionWarning
string gets lost in the noise of other logs.It's a pretty serious problem that I think deserves to be called out in the logs. Especially in production. #6000 will help but it still leaves many
void
.Looking for three approvals before merge, given how this affects workfow.
Security Considerations
--
Scaling Considerations
--
Documentation Considerations
--
Testing Considerations
--