Closed unicell closed 1 year ago
If you need a workaround for this, I've found that setting the go.mod
file to go 1.16
allows tools to be pinned correctly.
Is this perhaps related to issue https://github.com/golang/go/issues/54908 in Go?
Am I getting this right: it is a bug in Go and it will be fixed in Go 1.20?
I see similar issue when installing golangci-lint, even with Go 1.20. I've opened https://github.com/golang/go/issues/58388
It seems that the go list -mod=mod
command does not update the mod/sum files like go mod tidy
does. Bingo should perhaps do this instead:
go mod tidy
and go build
in that directory.Thanks for this, I was just investigating this. Especially https://github.com/golang/go/issues/58388 is super helpful 💪🏽
I assume the go mod tidy
does not have modfile flag...
I think the best way would be to create tmp dir only to execute go mod tidy and remove after done... PRs welcome, otherwise I will do it later this week.
Closing dup: https://github.com/bwplotka/bingo/issues/128
bingo version
output:v0.7
go version
output:go version go1.18.3 linux/amd64
What happened:
Failed to run
bingo get
for this particular go package.What you expected to happen:
Expecting
bingo get
to succeed, since:go install works just fine
and the underlying go build command
bingo
runs also works fine.How to reproduce it (as minimally and precisely as possible):
Logs (use
bingo get -v <thing you do>
for verbose output):Anything else we need to know: