Closed inceptchain closed 5 years ago
With the latest Go beta, those issues should not occur anymore. Make sure with the latest Go beta you use change all commands from using vgo
to go
.
I have the 1.10.3 go version, is that the correct one that I can use go rather than vgo?
On Wed, Aug 8, 2018 at 1:29 PM, Kenta Iwasaki notifications@github.com wrote:
With the latest Go beta, those issues should not occur anymore. Make sure with the latest Go beta you use change all commands from using vgo to go.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/perlin-network/noise/issues/136#issuecomment-411524251, or mute the thread https://github.com/notifications/unsubscribe-auth/AcaA_i8TEkeufE-GMEXIpPuEIFWp0viyks5uOzwSgaJpZM4ViV1X .
go 1.11+ is the correct one.
Shoud we update from 'vgo' to 'go' in readme ? I was confused for the first time
The README has now been updated to help users setup their projects more easily with Go 1.11+.
I am running into a vgo mod -sync error, that tells me it cannot find:
go: import "github.com/gogo/protobuf/protoc-gen-gogofaster/gocode/src/github.com/golang/mock/mockgen/tests/vendor_dep" -> import "a": cannot find module providing package a
I had an issue with protobufs 3.6 not working and versioned down to 3.5.1, that fixed the protobuf issue so maybe there are other versioning issues?
running ubuntu 18.04