You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Magister has added rate limiting a little while ago, and we currently just straight up ignore it. When ratelimited Magister sends an object like: {"Message":"Rate limit reached. Reset in 25 seconds.","SecondsLeft":25}.
I was thinking about when we get an object with a SecondsLeft field we delay every set request and repeat the current one (where we get the error from) after the value of SecondsLeft.
For this we need to wrap the HTTP object (as said in #29).
The text was updated successfully, but these errors were encountered:
Magister has added rate limiting a little while ago, and we currently just straight up ignore it. When ratelimited Magister sends an object like:
{"Message":"Rate limit reached. Reset in 25 seconds.","SecondsLeft":25}
.I was thinking about when we get an object with a
SecondsLeft
field we delay every set request and repeat the current one (where we get the error from) after the value ofSecondsLeft
.For this we need to wrap the HTTP object (as said in #29).
The text was updated successfully, but these errors were encountered: