on 429, retry `fetchAccount` instead of failing
What does this MR do?
when switching between accounts, with many tabs open (10 seem to be enough), they all hit the endpoint at the same time, and some get rate limited.
treating a 429 as a fatal error confuses the frontend, which ends up logging the user out of all their accounts.
this code makes the frontend retry, after waiting the appropriate amount of time.
seems to work fine in my testing.
thanks to @fEmber for noticing the problem!
Contribution Guidelines
By submitting this merge request, you agree to follow our Contribution Guidelines
-
I agree to follow this project's Contribution Guidelines -
I have made sure to test this merge request
Merge request reports
Activity
Filter activity
Please register or sign in to reply