last iteration is no reset and I still have a gap in my scalars
Hmm is this reproducible ? can you check with the latest clearml version (1.10.3) ?
btw: I'm assuming
I think I found the issue, the fact the agent is launching it causes it to ignore the "overridden"
What do you mean by?
We are able to
to 0 but not
Are you saying that if your code looks like:
Task.set_initial_iteration(0) task = Task.init(...)
and you abort and re-enqueue, you still have a gap in the scalars ?
Yes I am saying that not matter if we
set_initial_iteration(0) and also
continue_last_iteration=0 on the task init, if I requeue the task the last iteration is no reset and I still have a gap in my scalars
Let me know if you need more information of my env/worklow or need a dedicated issue
I had again the same problem but within a remote pipeline setup. The task launching the pipeline has
continue_last_task=0 but I guess this argument is not shared to the node/step that it will launched because when the
add_function_step is triggered we start to see again the offset inside the scalars of the node. Is there a way to inherit arg of the base task or something like that?