-
Notifications
You must be signed in to change notification settings - Fork 11
Handle UI runtime problems reported on Sentry #756
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
Conversation
| } | ||
|
|
||
| this._humanIdentifications = this._occurrence.identifications | ||
| .filter((i: any) => !!i.user) // Workaround to avoid crash when the backend is not returning any user |
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.
What about keeping the identification but showing an unknown user? I wonder if this happens when the user is deleted.
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.
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.
The delete explanation sounds possible, no further backend investigation needed then?
|
For the processing service problem discovered in #743 I have pushed a fix and updated the PR description. |
✅ Deploy Preview for antenna-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |


Here are our runtime errors reported on Sentry last 30 days (UI only).

In this PR we take care of issue 1 and 3. The other issues I think are related to request timeouts, they are more difficult to reproduce and I can't fully understand the details (they are not including any references to the frontend code base).
About the fixes: