You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the checksum from the code in github does not match the checksum saved in sum.golang.org. The v1.2.1 tag of github.com/argoproj/argo-rollouts might have been retagged after a minor edition on github. I guess you use proxy.golang.org to get dependencies, but that also shows that your project is depending on the copy of github.com/argoproj/[email protected] before its edition. Depending upon such inconsistent tag version may also result in some unexpected errors as well as build errors due to different proxy settings.
For example, when someone who does not use proxy.golang.org, say GOPROXY=direct, attempts to get github.com/argoproj/[email protected], the following error occurs.
So, this is a reminder in the hope that you can get rid of this problematic version of project github.com/argoproj/argo-rollouts.
Solution
1. Bump the version of dependency github.com/argoproj/argo-rollouts
I would recommend bumping the version of github.com/argoproj/argo-rollouts to a new release to ensure dependency copy in proxy.golang.org and github in sync.
Background
Repo
github.com/istio-ecosystem/admiral
depends ongithub.com/argoproj/[email protected]
.https://github.com/istio-ecosystem/admiral/blob/master/go.mod#L6
However, comparing version
v1.2.1
ofgithub.com/argoproj/argo-rollouts
from proxy.golang.org and github, there are inconsistencies.So the checksum from the code in github does not match the checksum saved in sum.golang.org. The
v1.2.1
tag ofgithub.com/argoproj/argo-rollouts
might have been retagged after a minor edition on github. I guess you use proxy.golang.org to get dependencies, but that also shows that your project is depending on the copy ofgithub.com/argoproj/[email protected]
before its edition. Depending upon such inconsistent tag version may also result in some unexpected errors as well as build errors due to different proxy settings.For example, when someone who does not use proxy.golang.org, say
GOPROXY=direct
, attempts to getgithub.com/argoproj/[email protected]
, the following error occurs.So, this is a reminder in the hope that you can get rid of this problematic version of project
github.com/argoproj/argo-rollouts
.Solution
1. Bump the version of dependency
github.com/argoproj/argo-rollouts
I would recommend bumping the version of
github.com/argoproj/argo-rollouts
to a new release to ensure dependency copy in proxy.golang.org and github in sync.References
The text was updated successfully, but these errors were encountered: