-
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
Bug in pipeline samples' parameters #478
Comments
This is one of the features we shipped recently. Users can specify the parameters directly(url='hello') instead of using PipelineParam class. |
I upgraded my SDK ( But I still get this error when I try to compile that file:
|
Could you try the newest version: pip3 install https://storage.googleapis.com/ml-pipeline/release/0.1.3-rc.3/kfp.tar.gz --upgrade. 0.1.2 is released a month ago without the new feature. 0.1.3-rc.3 works at my end. |
Yes, that works. Thank you |
…inable CEL Custom task (kubeflow#478) * add cel custom task poc * apply suggestions with minor fixes * add initial version of plugable cel template * fix lint * update staging code for converting containerOp to custom task * update staging code for converting containerOp to custom task * remove duplicate cel conditions * update flip-coin example to use custom task * update flip-coin example to use custom task * remove dsl dependencies; * add POC comments * fix lint * fix self-defined CEL custom task mapping * move custom task condition example to a separate folder * fix tests * make the new custom task spec and CEL condition feature as opt-in * update instructions and generalize custom task images * only let custom task result comparasion to skip the condition container to provide backward compatibility * only let custom task result comparasion to skip the condition container to provide backward compatibility * update example * update tests * fix comment
https://github.com/kubeflow/pipelines/blob/master/samples/basic/parallel_join.py#L25-L26 are not a
dsl.PipelineParam
as they should beThe text was updated successfully, but these errors were encountered: