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
After canceling a run, I tried to run az acr task logs. Even the command output the log, it didn't exit but still keep polling until timeout. We probably can check the run status beforehand and then download the log.
The text was updated successfully, but these errors were encountered:
What about timing out existing clients? I have a feeling we'd like to support that later once the entire E2E flow is done. But not sure how much value there even really is flowing cancellation from runner -> builder. More important if runner/builder start to be persistent.
I actually suggest a cheap fix in CLI command. First check if the run is in a terminated (eg, cancel, finish) state. If yes, try download the log once. Otherwise, polling the log until finish or timeout.
After canceling a run, I tried to run
az acr task logs
. Even the command output the log, it didn't exit but still keep polling until timeout. We probably can check the run status beforehand and then download the log.The text was updated successfully, but these errors were encountered: