SuccessfulKoala55 is this fixed in this release https://clearml.slack.com/archives/C03E7MNDG3C/p1651763847469039 ?

if this is a bug, I can raise an Issue in github and provide a snippet of code to reproduce it

upgraded to 1.3.2

Hi RattyLouse61 ,

Do you have an example of the parameters you're trying to connect?

I played a bit with it, it looks like it's caused by the 'None' in the dict. I think it would be nice if you opened a github issue 🙂

As a temporary solution you can use the following method - Task.connect_configuration()

Can you try upgrading and see what happens?

Let me take a look 🙂

RattyLouse61 , yep 🙂

CostlyOstrich36 thank you 🙂 I suppose the issues isn’t necessary if someone is already working on a fix?

RattyLouse61 I meant the version pf the clearml python package you're using when running the code, just do pip show clearml

ops. 1.1.6

SuccessfulKoala55 this is what I see on the Profile page:
WebApp: 1.3.1-169 • Server: 1.3.1-169 • API: 2.17

In [6]: type(conf["a"]["b"]["c"]["d"]) Out [6]: tuple

RattyLouse61 , one of the guys tells me that a fix will be pushed soon 🙂

I think so

Hey CostlyOstrich36 , the parameter I’m trying to log is a tuple (0, 100, None) and it’s stored in a nested dictionary. E.g.
{"a": {"b": {"c": (0, 100, None)}}}

Hi RattyLouse61 , what's the SDK version?

getting the same behaviour