Paul, Since the issue affected only a specific Linux user running beta2, I suspected it was a caching issuen then used "go clean -modcache" (as suggested in https://github.com/golang/go/issues/26695) to fix it. And it worked.
Unfortunately I don't know how to reproduce the caching (?) issue. I guess I should have saved the user's homedir for reference before running "go clean -modcache". I can no longer see the issue in beta2 or beta3... AFAICT modules are working like a charm. Everton Em quarta-feira, 8 de agosto de 2018 13:25:46 UTC-3, Paul Jolly escreveu: > > Everton - apologies, things got rather busy and this thread dropped > off my radar. > > Is it possible for you to test with the latest build of go from tip? > > There have been a number of fixes since beta3. > > Thanks > On Thu, 26 Jul 2018 at 16:13, Everton Marques <everton...@gmail.com > <javascript:>> wrote: > > > > > > Em quinta-feira, 26 de julho de 2018 12:05:18 UTC-3, Paul Jolly > escreveu: > >> > >> Just a quick check: what version of git are you using? > > > > > > $ git --version > > git version 2.17.1 > > > > $ go version > > go version go1.11beta2 linux/amd64 > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "golang-nuts" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to golang-nuts...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
