I think so, but haven’t investigated what is the problem exactly, I’ll report it though.

Huh, I see. Thanks for your answers. How difficult would it be to implement some way to automatically inferring repository information for components, or having a flag repo_inherit (or similar) when defining a component (which would inhering repository information from the controller)? My workflow is based around executing code that lives in the same repository, so it’s cumbersome having to specify repository information all over the place, and changing commit hash as I add new code.

@<1523701205467926528:profile|AgitatedDove14> I managed to fix the issue FYI. I replaced from clearml import PipelineDecorator with from clearml.automation.controller import PipelineDecorator and it suddenly works. What a weird issue.

Glad to hear that, indeed an odd issue... is this reproducible i.e. can we get something to fix it?

no worries @<1523701205467926528:profile|AgitatedDove14>

when I add repo="." to definition of all my component decorators it works (but not the pipeline decorator), but it doesn’t work without that part… the problem i’m having now is that my components hang when executed in the cluster… i have 2 agents deployed (default and services queues)

the components start hanging indefinitely right after printing Starting Task Execution

apologies @<1798887585121046528:profile|WobblyFrog79> somehow I missed your reply,

My workflow is based around executing code that lives in the same repository, so it’s cumbersome having to specify repository information all over the place, and changing commit hash as I add new code.

It automatically infers the repo if the original as long as the pipeline code itself is inside the repo, by that I mean the pipeline logic, when you run it the first time (think development etc), if it sits inside the repo it should auto detect it, if for some reason it does not work, try to pass repo="." to imply you have a local of the repo in the same folder, and from there it will autoi detect the repo detials. does that make sense ?

Hi @<1798887585121046528:profile|WobblyFrog79>

. When I execute the pipeline remotely in Kubernetes, those components

two things, one, make sure you specify the repo you need the components from in the decorator function, what will happen is the repo will be cloned into the container running on k8s, then inside the repo root your script (i.e. pipeline step) will be running.
None
second thing, if you need any of the other functions in the pipeline file, list then under helper_functions
None