-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
component/pipeline name clash: compiles fine, but causes run-time error #2993
Comments
Can you please check the SDK version. ( |
hmm... I did need to update kfp. However (not to sidetrack), while I can compile this example pipeline using kfp==0.1.38, when I compile the same pipeline using kfp>0.1.38 (including the latest 0.2.2), I get this error:
Has the API changed? |
Update: It looks like the compilation error comes from this
If I change that line to (I know this is 'forking' the topic, sorry-- if this is a real issue I'll file a sep. bug). |
I'll look into this. |
Thanks. And: at least with 0.1.38, the original 'name clash' issue is fixed. I assume that remains the case with newer releases. |
I've looked into the |
* Loosen ray range Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com> * Fix import of RayServeHandle ref ray-project/ray#34714 Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com> * Allow pandas 2.0 Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com> * Remove exclusion markers Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com> * Run poetry lock --no-update Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com> --------- Signed-off-by: ddelange <14880945+ddelange@users.noreply.github.com>
(This is with Build commit: ca58b22)
Running this pipeline gives the following run-time error, due to a name clash:

This issue was not caught at compile-time. And, I'd argue that it should be allowed and handled in some way (renaming the pipeline name in the yaml?) It breaks modularity to have to know the name of a component when loading it from a URL.
Here is the component definition.
The text was updated successfully, but these errors were encountered: