1534727 - Treestatus often gets stuck in a non-working state due to some sort of stale network state

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement)

Description

[Kartikaya Gupta (email:[e-mail])]

Attachment: Screenshot

My primary profile often runs into a problem where loading https://mozilla-releng.net/treestatus just gets stuck with the "Loading..." bar and doesn't actually load. At some point in the past this happened and after some debugging and IRC help we figured that it was a caching problem, and reloading the page with caching disabled fixed it. However that appears to no longer work (see attached screenshot).

The attached screenshot also shows a 400 error from a login.taskcluster.net request and I'm assuming that's the source of the problem but don't know how to resolve that. That request has no cookies either. I feel like the server should be doing things to make this not happen and am happy to debug more on the client side to figure out exactly what's happening, but would need some guidance as to where to start looking.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

Note that loading it in a different browser or profile works fine, so it must be related to state in my primary profile.

Comment 2

[Rok Garbas [:garbas]]

This is a known problem, but since there is a workaround and time pressure on other things I didn't dig deeper.

What happens is that authentication token either for auth0 or taskcluster expires (most likely a auth0 token) and we don't handle this case correctly. The temporary solution is to re-login.

I will put this on my backlog and hopefully I can allocate some time for this in the future.

Comment 4

[Rok Garbas [:garbas]]

This was fixed recently in https://github.com/mozilla/release-services/pull/2245