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 was archived by the owner on Nov 10, 2025. It is now read-only.
Difficult to pin down the specifics on this, but it could be related to issue #13 or vice versa.
It looks like no instances are temporarily available to serve traffic. Notably it does seem to happen when there is a short burts of traffic, akin to a new user or a couple of new users that suddenly and quickly use the marquee tool. Adding the warmup request has improved the situation.
Option 1 (not sure what option 2 is yet) is to reduce the concurrency on the api calls, as it maybe forcing the only serving instance to fail before the warmup request has made the next instance ready.
Difficult to pin down the specifics on this, but it could be related to issue #13 or vice versa.
It looks like no instances are temporarily available to serve traffic. Notably it does seem to happen when there is a short burts of traffic, akin to a new user or a couple of new users that suddenly and quickly use the marquee tool. Adding the warmup request has improved the situation.
Option 1 (not sure what option 2 is yet) is to reduce the concurrency on the api calls, as it maybe forcing the only serving instance to fail before the warmup request has made the next instance ready.