Yes, that's what I'm saying.

Where is the log of the Task that is created for the component?
The error you are getting is the Pipeline itself throwing error because the component Task failed, the question is why did the component Task failed

Hi, @<1523701205467926528:profile|AgitatedDove14>
I am attaching two log files.
One is the log file of the task that ran the pipeline code, and the other is the log file of the component.

Just to make sure, the first two steps are working ?
Maybe it has to do with the fact the "training" step specifies a docker image, could you try to remove it and check?
BTW: A few pointers
The return_values is used to specify multiple returned objects stored individually, not the type of the object. If there is a single object, no need to specify
The parents argument is optional, the pipeline components optimizes execution based on inputs, for example in your code, all pipeline components will be running in parallel, because they do not rely on the return value of one another, unless of course if you specify " parents " 🙂

Yes, here it is. Very simple code. Thanks 🙂

I wish I had a more detailed log file why task component failed, but that's all log files are.
The one line log file is the log of the component task.

Are you saying you have a single line in the console output of the component Task?

I'm running the main pipeline code remotely(not using run_locally).
The component in question seems to fail almost immediately after pipeline execution because of value error.
If I put docker argument in the decorator, value error appears and becomes failure..

Thanks @<1634001106403069952:profile|DefeatedMole42>
A follow up, (1) how are you spinning the agent ? (2) could it be the docker image "ultralytics/yolov5" does not have Bash as entry point ?
you can force that with

@PipelineDecorator.component(return_values=['int'], cache=False,
                             task_type='training',
                             docker="ultralytics/yolov5",
                             docker_args="--entrypoint /bin/bash",
                             parents=['preprocessing'])

I tested it with a simpler code to make it more clear!
I've attached the code and log files that I used.
It only fails if I use the docker image.. 😂
Thank you so much for pointing out the argument. I think I can use it better!!! 👍

Hi @<1634001106403069952:profile|DefeatedMole42>
This points to the pipeline component failing to execute (i.e. the Task of the component Failed)
Can you send the log of that Task?

How come the second one is one line?

How are you running it?

Hmm this is odd, could you provide the pipeline code maybe?