Open hxka opened 1 year ago
Yes that is intentional. Server errors are generally just warnings, but client errors indicate something's wrong on the client side, so they are hard fails.
Well, that's still a problem, as the next invocation of legendary would try to check for updates again, receive the same error, and crash again. In this case it made Heroic completely unusable - it kept executing legendary and it kept crashing.
http 429 is not a sorta a client error being the client has sent too many requests, but it's not a sorta thing that legendary has caused unless there was a big amount of requests which in this case no unless it was more widespread. Maybe wait 24 hours or so.
Here are two outputs of
legendary status
, one a few minutes after another:As you can see, legendary handles 503 returned by Epic servers gracefully, but crashes when it receives 429.