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

misc(error-reporting): report unhandled promise rejections #3886

Merged
merged 1 commit into from
Nov 23, 2017

Conversation

paulirish
Copy link
Member

Since we have a catch() way back in CLI, it's unlikely we'll actually have an uncaught rejection, but this is insurance anyhow.

Here's some reported unhandled rejections

Q: do we want to add any extra metadata to indicate this was unhandled?

@wardpeet
Copy link
Collaborator

seems solid :) 👍

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm, IMO we don't need any extra tags, won't the reason be clear its unhandled promise rejection?

@paulirish paulirish merged commit 9186735 into master Nov 23, 2017
@paulirish paulirish deleted the sentryunhandled branch November 23, 2017 00:29
@paulirish
Copy link
Member Author

Turns out I was reading the docs for browser javascript so this is implemented the wrong way. That said, it works and generally doesn't break things.

https://docs.sentry.io/clients/node/usage/#promises
https://github.com/getsentry/raven-node/blob/master/lib/client.js#L117-L124

whoops

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.

3 participants