-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
How to handle Argo as an dependency for Kubeflow pipelines. #3803
Comments
The validate library transitively imports this HDFS dependency:
|
That tag does not exist, try pinning to v1.13: go get github.com/colinmarc/hdfs@v1.1.3 |
Thanks @alexec. When i pin to 1.13 I get the following issues when I run the test for the validation argo workflows in the Kubeflow backend.
Link to test. The test works when I have github.com/colinmarc/hdfs v1.1.4-0.20180805212432-9746310a4d31, which confuses me a bit .... |
Get the same error as #1983 if i pin to v1.1.3 issues discuss but don't get it to work with their solution either. |
Do you know more about the issue @alexec, thanks for your help! |
hi @NikeNano I'm afraid I don't know how to fix this issue. The is Go modules issue rather than an Argo issue. You'll know if you've tried to import the Kubernetes dependencies Go modules is not the seamless experience of Maven. |
Thanks for the help :)
I am starting to learn that now .... :( |
I believe #3991 would help the overall situation. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Summary
For Kubeflow pipelines Argo Workflows are used. During attempts to do validation of Argo Workflows in the backend of Kubeflow pipelines there are some issues with dependencies on com_github_colinmarc_hdfs that comes from having argo as a dependency.
For Kubeflow pipelines Bazel is used. To reproduce pull the branch from here: kubeflow/pipelines#3965
Then execute:
bazel run //:gazelle -- update-repos --from_file=go.mod & bazel build --action_env=PATH --define=grpc_no_ares=true //backend/...
The received error message is:
How could this dependency be handle correctly? I am rather new to both golang and Bazel so sorry if I am missing something obviously.
Thank you!
Motivation
Why do you need to know this, any examples or use cases you could include?
The text was updated successfully, but these errors were encountered: