Plyr throwing exceptions. Can we catch?
These exceptions might be harmless but they are muddying up Sentry and should be caught.
- https://sentry.io/organizations/minds-inc/issues/1384098907
- https://sentry.io/organizations/minds-inc/issues/1177357869
- https://sentry.io/organizations/minds-inc/issues/1384007806
- https://sentry.io/organizations/minds-inc/issues/1384675732
- https://sentry.io/organizations/minds-inc/issues/1384120447
- https://sentry.io/organizations/minds-inc/issues/1384999350
- https://sentry.io/organizations/minds-inc/issues/1384970051
- https://sentry.io/organizations/minds-inc/issues/1383435876
added scoped labels
assigned to @benhayward.ben
added scoped label
added scoped label
unassigned @markeharding
- Developer
Discussed in meeting just now,
Emi pointed out the error is in a promise in their code, so we cannot catch it.
First step I'm going to look into whether there is a config option to silence the errors. Second step I'm going to post on Playrs Github/Gitlab.
If we still cannot silence the errors, we plan to look into whitelisting in Sentry.
added scoped label
- Developer
I think this could be an issue with the Plyr wrapper, ngx-plyr, though the error does explicitly occur within the core Plyr package. I am going to spend a further 30 minutes looking at whether it could be a misconfiguration issue.
added 30m of time spent at 2020-01-06
- Developer
https://sentry.io/organizations/minds-inc/issues/1177357869/
May be solvable as that isn't too similar to the rest of the errors there. https://github.com/sampotts/plyr/issues/331
mentioned in merge request !712
added 3h of time spent at 2020-01-06
added scoped label and automatically removed label
- Developer
Please do not close this card with the above MR.
added scoped label and automatically removed label
added scoped label and automatically removed label
- Developer
I did go ahead and get my own local working version of Sentry, and with help from Brian worked out that we should be able to use the handleError, ignoreError or beforeSend. Unfortunately, the error jumps over all of these, as its being bounced to the main angular error handled.
Relevant GitHub https://github.com/getsentry/sentry-javascript/issues/2169#issuecomment-525722319Unfortunat
In terms of if we do get a filter system to work, the errors above are different, and we don't want to blanket ignore all errors of these types:
-
NotAllowedError https://sentry.io/organizations/minds-inc/issues/1384970051/?project=1538008
-
NotSupportedError https://sentry.io/organizations/minds-inc/issues/1384675732/?project=1538008
-
TypeError in Globalhandler https://sentry.io/organizations/minds-inc/issues/1384098907/?project=1538008 https://sentry.io/organizations/minds-inc/issues/1383435876/?project=1538008 https://sentry.io/organizations/minds-inc/issues/1384999350/?project=1538008 https://sentry.io/organizations/minds-inc/issues/1384120447/?project=1538008 https://sentry.io/organizations/minds-inc/issues/1384007806/?project=1538008
-
UnhandledRejection https://sentry.io/organizations/minds-inc/issues/1177357869/?project=1538008
So what we would have to do is suppress all errors originating from plyr, even if they're useful to us.
At the moment I'm digging around and trying to get a hook into Sentry before the XHR sends, so that I can interrupt it and add this filter.
-
added 2h of time spent at 2020-01-08