-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
fix: Rrror parser throw #1225
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: Rrror parser throw #1225
Conversation
|
YunFeng0817
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.
This change makes sense.
* Warn instead of throwing error when parsing for console logs * Added error to warning
* Warn instead of throwing error when parsing for console logs * Added error to warning
* Warn instead of throwing error when parsing for console logs * Added error to warning
* Warn instead of throwing error when parsing for console logs * Added error to warning
* Warn instead of throwing error when parsing for console logs * Added error to warning
* Warn instead of throwing error when parsing for console logs * Added error to warning
The error parser can throw if it fails to parse the error which is very meta. This ends up being logged / caught in Sentry which is unnecessary.
Changes
Rather than wrapping all of the places it is used, simply changes the function to return cleanly with a warning