You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
m-dz
changed the title
[bug] <Bug Name>
[bug] For loops in nested pipelines have clashing names
Dec 23, 2024
m-dz
changed the title
[bug] For loops in nested pipelines have clashing names
[bug] For loops in nested pipelines have clashing component names
Dec 23, 2024
Environment
Python 3.10.13
KFP SDK version:
2.11.0 (current on 23/12/2014)
Steps to reproduce
Simple example with:
What I think is happening when pipelines are being merged:
Expected result
Expected behaviour can be obtained by making two relatively simple changes in the
TasksGroup
class:self.name = name
in https://github.com/kubeflow/pipelines/blob/master/sdk/python/kfp/dsl/tasks_group.py#L69 , which provides a name for the component to use_make_name_unique
method (https://github.com/kubeflow/pipelines/blob/master/sdk/python/kfp/dsl/tasks_group.py#L87) from it, which stops the name to be overwrittenMaterials and reference
The following 2 files reproduce the issue:
Labels
/area components
Impacted by this bug? Give it a 👍.
The text was updated successfully, but these errors were encountered: