I was having this confusion as well. Did behavior for execute_remote change that it used to be Draft is Aborted now?
Actually it was changed, it used to reset the Task (then push into into execution queue if needed), with clearml v1.0, we now support pushing aborted Tasks back into queues, so execute_remotely aborts the Task (instead of reseting it)
(you can always manually reset it)
Not that I know of... Is there an agent waiting on the queue? If so, can you try without an agent listening on the queue?
I was having this confusion as well. Did behavior for execute_remote change that it used to be Draft is Aborted now?
Nothing except that Draft makes sense feels like the task is being prepped and Aborted feels like something went wrong
Yes guess that if we call execute remotely, without a queue, it makes sense for you to edit it...
Is that the case TrickySheep9 ?
If it is I think we should change it to draft when it is not queued. sounds good to you guys ?
Any specific use case for the required “draft” mode?
Nothing except that Draft makes sense feels like the task is being prepped and Aborted feels like something went wrong
New user is trying to push tasks, and the task is instantly changed to aborted from running
TenseOstrich47 , what do you mean exactly? Every task you run ends on 'aborted' status?
It should be a draft, so that it can be enqueued
Ok, that explains a lot. The new user was using version 1.x.x and I was using version 0.17.x. That is why I think my task was being drafted. and his was being aborted.
There is no specific use case for draft mode - it was just the mode I knew that I understood to be used for enqueuing a newly created task, but I assume that aborted now has the same functionality
Any specific use case for the required "draft" mode?
TenseOstrich47 , can you please describe what your usage is?