Ah right, nice! I didn’t think it was as I couldn’t see it in the Task reference , should it be there too?
I guess two more straightforward questions:
Could it be made possible for task.execute_remotely(clone=False, exit_process=False) to not raise an exception? Im happy work on a PR if this would be possible Is there any issue to having task.reset() in the public API/is there any potential issues with using?
Hi SuperiorPanda77 , I'm not sure I understand, can you elaborate on the specific use case?
Another option would be to dotask.close() task.reset()And then execute an agent to pick up that task, but I don’t think reset is part of the public API. Is this risky?
Will do! What’s the process for adding task.reset to the public API, just adding it to the docs?
Hi CostlyOstrich36 , thanks for getting back to me!
I want to launch multiple tasks from one python process to be run by multiple agents simultaneously.
My current process for launching one task remotely is to use task.execute_remotely , and then I separately spin up a VM and execute a ClearML agent on that VM with the task ID.
Ideally, I would like to create multiple tasks in this way - so do Task.init(…) , set up some configuration, and then task.execute_remotely in a loop.
I can’t do this as execute_remotely exits the process unless clone=True , which I don’t really want to do.
Let me know if I can clarify further
Hi @<1523701092473376768:profile|SuperiorPanda77> , I think a PR would always be appreciated. I don't see any issues with using task.reset()