fix(js): improved, unambiguous error message#1428
Merged
Conversation
subzero10
changed the title
Member
Author
|
Looks like integration tests are failing but the issue is unrelated to this PR. We can go ahead and merge and I will fix those in a separate PR. |
stympy
approved these changes
Feb 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Status
READY
Description
Before exiting the process due to uncaught process exceptions or unhandled promise rejections we were logging the same error message, which recently cost hours of debugging for a customer. This should make it easier to identify whether the error originated from (uncaught exception or unhandled rejection).