-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
dependency analysis issue with 'component.yaml'-based ops #941
Labels
Comments
Thank you for discovering this DSL compiler bug. I've submitted PR fixing it. |
k8s-ci-robot
pushed a commit
that referenced
this issue
Mar 8, 2019
Thanks for the quick fix, Alexey. |
cheyang
pushed a commit
to alibaba/pipelines
that referenced
this issue
Mar 28, 2019
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
Fix postsubmit PR link
HumairAK
pushed a commit
to red-hat-data-services/data-science-pipelines
that referenced
this issue
Mar 11, 2024
…eflow#941) * Loop ranges should handle start = 0 and end = 0, should generate one iteration. * When from = to, then generate one iteration. emulating how enumerate works. * Fixed edge cases. * if from and to are unset, we should not pick defaults either.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I built this pipeline to play around with the new
load_component_from_url
functionality: https://gist.github.com/amygdala/f6ac2224c598e8355763a45ab502cb49(The pipeline doesn't quite have correct functionality yet, but that's not important to this issue).
Note line 72, using the
op2.after(op1)
statement.When I compile this file, I get the following error. To me it looks like the dependency analysis is trying to use the 'human name' for the component rather than its 'name'.
I'm using the 0.1.12 sdk. (If I comment out line 72, it compiles properly).
The text was updated successfully, but these errors were encountered: