Closed lissyx closed 1 year ago
Looks to be intermittent, a fifth retry works
I am on PTO and on the go, this is likely bad cached data so should be back to normal after cache expiration (15mn), if bot please ping relman on slack or ask our sre team for a redeploy (that will empty the.entire cache)
Le mer. 16 août 2023, 11:45, lissyx @.***> a écrit :
Looks to be intermittent, a fifth retry works
— Reply to this email directly, view it on GitHub https://github.com/mozilla/releases_insights/issues/50#issuecomment-1680856910, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADO5Z5RNR6ZTTO5CBQYLMTXVTTKZANCNFSM6AAAAAA3SXQY2M . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I'm also on parental leave otherwise I'd pinged people directly 🥴
This is fixed by a redeploy, it wasn't a caching issue as the 500 errors were intermittent and the cache should have long expired. There was also no sentry alert and no recent code changes, so it doesn't seem code related. Maybe the docker image was in a bad state.
For me the main entry point https://whattrainisitnow.com is just white page. The code we have at https://github.com/mozilla/process-top-crashes/actions/runs/5874169649/job/15947783430 is also reporting failures (
req.ok
is notTrue
) when querying for versions.