Upgrade dependency "github.com/opensearch-project/opensearch-go"
Ben131-Go opened this issue · comments
Background
Repo github.com/Isan-Rivkin/surf
depends on github.com/opensearch-project/opensearch-go@v2.0.0
.
https://github.com/Isan-Rivkin/surf/blob/main/go.mod#L24
However, comparing version v2.0.0
of github.com/opensearch-project/opensearch-go
from proxy.golang.org and github, there are inconsistencies.
"committer": {
"name": "Vacha Shah",
"email": "vachshah@amazon.com",
"date": "2022-06-16T17:52:10Z"
}
{"Version":"v2.0.0","Time":"2022-06-15T17:15:04Z"}
So the checksum from the code in github does not match the checksum saved in sum.golang.org. The v2.0.0
tag of github.com/opensearch-project/opensearch-go
might have been retagged after a minor edition on github. Depending upon such inconsistent tag version may 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/opensearch-project/opensearch-go@v2.0.0
, the following errors occur.
go: downloading github.com/opensearch-project/opensearch-go/v2 v2.0.0
go: github.com/opensearch-project/opensearch-go/v2@v2.0.0: verifying module: checksum mismatch
downloaded: h1:iG0+zWWfNQwxUEBcTLEdT3RmVmJohnuT3TJhOSvQI/s=
sum.golang.org: h1:Ij3CpuHwey29cYPVMgi5h1pWBH2O0JaTXsa4c7pqhK4=
SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.
For more information, see 'go help module-auth'.
So, this is a reminder in the hope that you can get rid of this unreliable version of project github.com/opensearch-project/opensearch-go
.
Solution
1. Bump the version of dependency github.com/opensearch-project/opensearch-go
I would recommend bumping the version of github.com/opensearch-project/opensearch-go
to a new release to ensure dependency copy in proxy.golang.org and github in sync.
References
Hi @Ben131-Go and thank you for the very informative and clear issue 👍
I will do my best to prioritize it, (see to-prioritize
label), once that label removed it means theres active work on it.
I will update here with PR.
In the mean time is this a blocker for you?
If so, please feel free to open a PR with a fix.
Thanks for your quick reply! This is not a blocker for me at the moment. This issue is just a small kind reminder.
@Ben131-Go Thanks!