With --full-isolation, package fails to import its own internal packages about vg HOT 4 CLOSED

There are two distinct problems here:
First is minor: The README already talks about go tooling's problems with relative paths with --full-isolation. This is another instance of that.

$ go build hello 

works under some conditions.

• The README could do with an extra hint that 'go build .' will also fail (and possibly in this weird way, complaining about internal package imports).

The second problem is that to get to the good case above, I had to clear the env before 'vg init'
I did:

vg destroy
rm .virtualgo
sudo -u callpraths bash
vg init
go build hello
# works

Looks like we're leaking some env variables from earlier vg invocations in a way that when we run vg init later, we do not call ws.InstallLocalPackagePersistently in initSettings.go because GOPATH is found to not be a prefix of cwd.

from vg.

Thanks for the bug report. I'll add the internal package problem to the README in the section with the problems that using absolute paths fixes.

For your second problem I'm a bit confused about how you got in the broken state, but it indeed sounds like a bug. Could you make a separate issue for that problem with full steps for reproducing it? Because it seems quite unrelated to the internal packages problem.

from vg.

Just updated the README with this issue.

from vg.

I'm gonna close this, since I updated the README. Please open a new issue for the second problem you ran into.

from vg.