-
Notifications
You must be signed in to change notification settings - Fork 44
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: prevent invalid error stack traces #617
Conversation
Codecov Report
@@ Coverage Diff @@
## main #617 +/- ##
==========================================
- Coverage 66.70% 66.65% -0.06%
==========================================
Files 130 130
Lines 6007 6009 +2
Branches 1137 1141 +4
==========================================
- Hits 4007 4005 -2
- Misses 1636 1639 +3
- Partials 364 365 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Asset Size ReportMerging this pull request will result in the following CDN asset size changes:
Merging this pull request will result in the following NPM package consumer size changes:
Other Standard CDN AssetsReleased Assets
Built Assets
Other Polyfill CDN AssetsReleased Assets
Built Assets
|
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.
Some of the tests need re-adjusting
Verified the Safari 15 test failures were due to known SL Safari15 issues. |
Removing the instantiation of the Error class in the jserrors feature for instances where a non-Error value is thrown from customer's code. In such cases, an Error instance would be created and the stack trace would point back to the agent code as the source. This causes confusion since it makes it seem like the agent code is throwing the error when that is not the case. Instead, the internal UncaughtError class will be used and no stack trace will exist.
Overview
Addressing PR comments from #614.
Related Issue(s)
https://issues.newrelic.com/browse/NR-138375
Testing