This was with using one task in a multiprocessing.pool and the next one in the main process. I switched to have all tasks in a separate process via ProcessPoolExecutor and now it runs fine 👍 (version 0.17.5)
GreasyPenguin14 whats the clearml version you are using, OS & Python ?
Notice this happens on the "connect_configuration" that seems to be called after the Task was closed, could that be the case ?
yes that makes send, I think what happened is one of the processes completed the Task (i.e. closed it) before the others did, and so they threw exception.
I switched to have all tasks in a separate process
I think that's probably the best (performance wise as well), nice!
Hi GreasyPenguin14 , can you share an approximate snippet of your code?