Dear @<1523701205467926528:profile|AgitatedDove14> and @<1523701435869433856:profile|SmugDolphin23> , i think i have noticed another interesting effect of decorators. When pipeline method has a custom wrapper (decorator) and I trigger the pipeline from clearml UI, then parameters that are provided via the UI are not actually passed to the pipeline method. At the same time custom decorators used on pipeline components and simple functions works exactly the same both when I trigger pipeline ...

Hi @<1523701205467926528:profile|AgitatedDove14> , thank you very much, it solved my issues!

@<1523701205467926528:profile|AgitatedDove14> thank you very much for update! I am looking forward to the RC :)

Hi @<1523701205467926528:profile|AgitatedDove14> , i got a strange behavior also with this RC. For pipeline itself and simple functions it works well as before. But for pipeline components I still get an error. Below are some examples based on the code I have shared initially (I have slightly modified it).

With the old clearml version 1.12.2.

If I remove @my_decorator from my_pipeline_component_with_wrapper pipeline runs successfully and produces following output:

--- main started
...

@<1523701205467926528:profile|AgitatedDove14> , thank you, I am looking forward for any updates. By the way, I am running pipeline with a poetry script, but I do not think it is relevant to the use of decorators.

Hi @<1523701205467926528:profile|AgitatedDove14> , thanks for the update and for the fix. This RC works well on my test code when I place custom decorator under pipeline decorator, which is great. The other order (with custom decorator above pipeline fails - just for you info 🙂 ) I will soon update my production code and will let you know if I notice any side effects.

@<1523701205467926528:profile|AgitatedDove14> , I am not sure if it is a side effect of this fix, but with the new version of clearml, when I run pipeline locally it is no longer being reported to the server. Each step is reported separately in experiments, but no new run is visible in the "Pipelines".

@<1523701205467926528:profile|AgitatedDove14> , the issue is present with 1.13.3rc1 for me as well. With 1.13.2 pipeline is correctly reported.

@<1523701205467926528:profile|AgitatedDove14> , great, thank you for reacting so fast :)

@<1523701435869433856:profile|SmugDolphin23> , looks good, I can see the pipeline again. Thank you for a quick fix!

@<1523701435869433856:profile|SmugDolphin23> thank you for such a detailed explanation! I will give it a try now :)

Hi @<1523701435869433856:profile|SmugDolphin23> , thank you for getting back to me. I actually have my Enum in a separate file. I have tried importing it both to the context (file with pipeline component) and to inside of the pipeline component function. Unfortunatelly it does not work. The same scenario for pipeline itself works perfectly fine (when Enum is imported to the context, aka .py file with pipeline code).

Important : it only fails when default value is provided. Simply defin...