BUG: common unknown "there's been an error"

[codecovdesign]

Problem to solve

This is an ongoing bug worth resurfacing. I think most have seen it personally; and in the video below we see the user frustration. In that session it happened so much that the testing took 2-3x longer and the user even changed browsers (safari to chrome) AND removed ad blocker, yet it persisted on both browser. The error appears at anytime seemingly randomly, so it's challenging to pinpoint the exact root.

GH-1410_p1.mp4

Investigation

Identify the root of this and potential steps to resolve.

[eliatcodecov]

This one will likely take a lot of effort to run down, could be a useful bug for someone newer to the codebase. Maybe @ajay-sentry ? Will leave it to @katia-sentry to decide.

[nicholas-codecov]

This is a extremely tricky bug to find, it will occasionally happen when you're not expecting it, so you refresh to get rid of it ... it than clears and doesn't come back. You basically need to sit on a page with your network tab open and recording the requests to hopefully catch it.

[ajay-sentry]

@eliatcodecov @nicholas-codecov Any idea if this could be something that might be easier to uncover once source maps are loaded up properly on our sentry integration? Saw we recently merged this, though looking at sentry I don't see the changes taking effect just yet https://github.com/codecov/gazebo/pull/2735/files

[nicholas-codecov]

Source maps are working, old issues however remain unmapped, also users have to be using the latest version which may take a second.

[ajay-sentry]

@nicholas-codecov got it, makes sense. Im still seeing some minified issues come in as recent as 4 hours ago but will keep checking back

[nicholas-codecov]

can you link the issues?

[ajay-sentry]

Here's one: https://codecov.sentry.io/issues/5140541216/?project=5514400&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=7d&stream_index=16

[ajay-sentry]

One more 3 hours ago: https://codecov.sentry.io/issues/5140973564/?project=5514400&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=7d&stream_index=8

[nicholas-codecov]

Okay, yea even tho these are new ... they're on an old version of Gazebo, looking at some other issues everything seems to be alright

[nicholas-codecov]

If there are more and more issues that aren't being resolved in a couple days I'll dig into it w/the Infra folks

[ajay-sentry]

yep yep sg!

[drazisil-codecov]

I think this is same error that now displays as a random 404. As far I can tell, it's actually a 403 response from /user

Doesn't seem to matter if I'm logged in or not.

[ajay-sentry]

@drazisil-codecov Have you run into this one recently? I think we've done some work on the UI side to fix, can reopen if needed