Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Get rid of ignoreErrors
See original GitHub issueThis is a remnant of pre 1.0 days with the "Script error." issue, but this has since been hardcoded into raven. It doesn’t really help with anythign else.
Issue Analytics
- State:
- Created 11 years ago
- Comments:18 (10 by maintainers)
Top Results From Across the Web
IgnoreErrors regex not removing error from sentry
Hi I have been running some tests on a js frontend and i get an error that i would like to ignore. I...
Read more >How to undo "Ignore errors like this"?
I know that if you put the caret on a specific warning (in my case a PEP8 warning) and press Alt-Enter, you can...
Read more >How to globally ignore errors with sentry v5 to reduce noise
There seems to be an ignoreErrors config option. It's documented in their example app here:.
Read more >Ignoring Errors - PHPStan
Errors can be ignored by adding a regular expression to the configuration file under the ignoreErrors key. To ignore an error by a...
Read more >Ignore errors on multiple rows - Microsoft Community
Is there a way to ignore errors on multiple rows without having to click into each cell and click ignore error? I have...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve got tons of errors I ignore. Why is this being removed? For example - I was continually getting an error that I finally traced back to be some random Firefox plugin that generated a spurious error. There was nothing I could do about it - so I added it to ignoreErrors.
I reverted this deprecation warning. It’s just a bad idea. 😃
Thanks for the input guys!