I've also mentioned it on the issue I created but I had the issue even when I set the type to bool in parser.add_argument(type=bool)

However when i'll reset or clone the task, now it won't just accept the default value but clearml will pass the arg directly

okay thanks! let's pick it up on github 🙂

I'll create a github issue. Overall I hope you understand.

Basically if I pass an arg with a default value of False, which is a bool, it'll run fine originally, since it just accepted the default value.

I think this is the nargs="?" , is that right ?

Yep, and this is the root cause of the issue (But easily fixable) 🙂

Hi VexedCat68
can you supply more details on the issue ? (probably the best is to open a github issue, and have all the details there, so we have better visibility)
wdyt?

Yeah

And casting it to bool converts it to True

only issue is even though it's a bool, it's stored as "False" since clearml stores the args as strings.

(basically python abusing types/casting where the value can be both str/bool on the same argparser aergument)

Basically if I pass an arg with a default value of False, which is a bool, it'll run fine originally, since it just accepted the default value.

It was nargs="?" I think