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
I think that if an unmanaged pod (from a task run or a deploy) has been pending for more than a certain number of seconds (30? 60?), we should emit a warning. We could also have the pod time out at that point, but I'm not really comfortable doing that based on the generic status of "Pending" alone. So logging a warning (which should include the pending reason) seems like a good place to start.
The text was updated successfully, but these errors were encountered:
This reminds me of a pattern I saw in Vertx, which has an event loop that you're not supposed to block for more than X seconds. If you do, you get repeated warnings and are meant to investigate.
Valuable takeaway perhaps is once the user sees the warning, investigates, and determines they can't reduce the time within the window, giving them some way to override the setting might be good. I've seen many people ask in the community about how to turn off the warning 😄
Follow-up to #337
I think that if an unmanaged pod (from a task run or a deploy) has been pending for more than a certain number of seconds (30? 60?), we should emit a warning. We could also have the pod time out at that point, but I'm not really comfortable doing that based on the generic status of "Pending" alone. So logging a warning (which should include the pending reason) seems like a good place to start.
The text was updated successfully, but these errors were encountered: