-
Notifications
You must be signed in to change notification settings - Fork 641
Remove uncaught interface #2208
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
Remove uncaught interface #2208
Conversation
ofrobots
left a comment
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 think the README.md changes are missing.
8286972 to
ccd0553
Compare
|
@ofrobots my bad -- weird rebase flow. Changes added |
ccd0553 to
ec21135
Compare
packages/error-reporting/README.md
Outdated
| errors.report(new Error('Something broke!')); | ||
| ``` | ||
|
|
||
| - *One may even catch and report application-wide uncaught errors:* |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
packages/error-reporting/README.md
Outdated
|
|
||
| ```js | ||
| var errors = require('@google-cloud/error-reporting')(); | ||
| process.on('uncaughtException', e => errors.report(e)); |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
bfe989f to
fb23ced
Compare
|
@ofrobots updated |
|
@ofrobots let me know when you're happy with this and I'll try to merge within 10 seconds. |
packages/error-reporting/README.md
Outdated
| process.on('uncaughtException', e => errors.report(e)); | ||
| process.on('uncaughtException', (e) => { | ||
| // Write the error to stderr. If one does not manually do this | ||
| // nothing will be printed before the VM exits. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
packages/error-reporting/README.md
Outdated
| - *One may even catch and report application-wide uncaught errors:* | ||
| - **One may even catch and report application-wide uncaught errors:** | ||
| - *It is recommended to catch uncaughtExceptions for production-deployed applications* | ||
| - [To read more about uncaught exception handling in Node.js and what it means for your application please click here](https://nodejs.org/api/process.html#process_event_uncaughtexception) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
fb23ced to
9116a94
Compare
|
@ofrobots updated |
ofrobots
left a comment
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. Is this blocked on #2189?
|
Is this really over? |
|
No not yet, sorry was trying to see if closing this had an effect on the PR file propagation for the CI integration |
9116a94 to
6c1e4b4
Compare
|
@stephenplusplus @ofrobots merge conflicts resolved! |
6c1e4b4 to
54a6ead
Compare
Blockers
Remove Uncaught Exception Handler
Note: