Skip to content
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

getNotifications is returning 500 code errors #13131

Closed
Tracked by #13124
easyCZ opened this issue Sep 20, 2022 · 3 comments · Fixed by #13178
Closed
Tracked by #13124

getNotifications is returning 500 code errors #13131

easyCZ opened this issue Sep 20, 2022 · 3 comments · Fixed by #13178
Labels
team: webapp Issue belongs to the WebApp team

Comments

@easyCZ
Copy link
Member

easyCZ commented Sep 20, 2022

Dashboard
Screenshot 2022-09-20 at 15 44 55

query: sum(increase(gitpod_server_api_calls_total{method="getNotifications"}[7d])) by (statusCode)

@easyCZ
Copy link
Member Author

easyCZ commented Sep 22, 2022

@jankeromnes Landing #13178 caused this issue to close. But I believe the fix introduced does not actually fix the API returning 500 errors - it handles them on the UI side but does not stop them from happening server side. Are you happy for me to re-open?

@jankeromnes
Copy link
Contributor

jankeromnes commented Sep 22, 2022

Hi @easyCZ! 👋

it handles them on the UI side but does not stop them from happening server side

Actually, #13178 handles them server side 😇

Screenshot 2022-09-22 at 09 51 38

And looking at the code, I'm pretty sure that this does fix the API returning 500 errors (unless super throws, but that seems unlikely).

But please do re-open this if you notice more 500 errors from this call post deployment. 👍

@easyCZ
Copy link
Member Author

easyCZ commented Sep 22, 2022

Thanks @jankeromnes, I must have confused the PRs. This does look like it indeed handles them. I'll do some validation on this from the metrics side post rollout and will re-open if we continue to see issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: webapp Issue belongs to the WebApp team
Projects
None yet
2 participants