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
{{ message }}
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
During deploys, or even in normal operation when a user leaves, we don't clear the node until a message hits. For this, we return a 503 with errno 202. The error returned however says "Service Unavailable". That's quite false, the service is fine, the 503 is intentional and the request should be retried. We should not say the service is unavailable.
The text was updated successfully, but these errors were encountered:
During deploys, or even in normal operation when a user leaves, we don't clear the node until a message hits. For this, we return a 503 with errno 202. The error returned however says "Service Unavailable". That's quite false, the service is fine, the 503 is intentional and the request should be retried. We should not say the service is unavailable.
The text was updated successfully, but these errors were encountered: