From what I've seen, another fix would be to pass a default value to your parameters, for example: def executing_pipeline(start_date=0, end_date=0):
Hey SuccessfulKoala55 currently using the clearml
package version 1.7.1
and my server is a PRO SaaS deployment
I had the same issue, they fixed it in 1.7.2rc1 I think. You can try pip install clearml==1.7.2rc1
Okay I confirm having default parameters fixes that issue, but kinda sad to have lost 3 days into that super weird behavior
And running with a Python 3.10
interpreter
Hi FierceHamster54 , which clearml version are you using?
Yeah me too, I had no idea what was happening 😅
Nope sorry I don't have that, but this was our discussion about it: https://clearml.slack.com/archives/CTK20V944/p1665477602050259
FierceHamster54 1.7.2 will be released very soon 🙂
Nice it works 😍
I'll try to update the version in the image I provide to the workers of th autoscaler app (but sadly I don't control the version of those in itself since it's CLearML managed)
Apparently, the issue is that it will always pass None
if there's no default value
pip package clearml-agent
is version 1.3.0
Seems pretty critical tho, SuccessfulKoala55 is the 1.7.2
releasing soon ? ( I see the rc2 has been built 3 days ago)
I'm looking for the github issue so I can check the PR fixing that, do you have any info on that ?
And remote workers are managed by the GCP auto-scaler app so I presume those clearml-agent
are up-to-date too