-
Notifications
You must be signed in to change notification settings - Fork 71
Failed to fetch common module #70
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
@hzxuzhonghu , please also help to check this :) |
/assign |
@Jeffwan It is not the pr i filed introduced this issue.
|
with |
Not sure why, it is weird how i can import latest from tf-operator. |
@hzxuzhonghu I am not 100% sure this is related to the PR. Technically, once we replace libraries, it should be fine. Let me double check my environment. I can confirm that if I import this separately, both latest and previous one won't work. This is expected because go.mod in current project ( not kubeflow/common) doesn't have replace. |
@hzxuzhonghu @k82cn I think I figure it out. Sorry about the confusion. If one project doesn't have all component replaced, it may have this issue. In order to use |
For those meeting the similar issue: kubernetes/kubernetes#79384 (comment) |
This is interesting. I notice I think the problem is more on the Kubernetes side. most of the components including Since we upgrade to 1.18 in PR #62, this requires a change on the operator which uses this lib to have a separate record to override |
Even we replace all kubernetes dependencies in go.mod, we want to use lowest version to avoid potential dependency issues. See kubeflow#70 for more details. Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com>
* Update go.mod to use lowest Kubernetes version Even we replace all kubernetes dependencies in go.mod, we want to use lowest version to avoid potential dependency issues. See #70 for more details. Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com> * Move Pods/Services CRUD to separate control folder Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com>
Even we replace all kubernetes dependencies in go.mod, we want to use lowest version to avoid potential dependency issues. See kubeflow#70 for more details. Signed-off-by: Jiaxin Shan <seedjeffwan@gmail.com>
Following command doesn't work.
I think this is because of #62.
I use the stable version here for now and I will fix this when I get time.
The text was updated successfully, but these errors were encountered: