After upgrade to GO extension 0.6.56 version, some errors about package

[amnotbusy]

win7 64bit
vscode 1.10.2
how to fix it? thx

[amnotbusy]

[amnotbusy]

@mattetti @buckett @saml @AlekSi @neelance reinstall golang vscode and tools,this bug still here

[amnotbusy]

[ansencumt]

I also get the same error.

[ansencumt]

The word "ode" is not exist in my system folder.

[amnotbusy]

I build 0.6.54, install it can work normal, remenber uninstall 0.6.56 first
Open the extensions menu in VSCode and choose Install from VSIX and select the Go-xxx.vsix
I upload zip file failed, share url to download Go-0.6.54.vsix

[amnotbusy]

@ansencumt

[ansencumt]

@a57571735 thx

[nezorflame]

getting the same issue on MacOS.
seems like it somehow trims the start of the package name thus failing to find the package.
@lukehoban @ramya-rao-a please take a look.

[nezorflame]

Here's the previous build for the time being for those who like me are unable to install from previous link by @a57571735
Go-0.6.54.vsix.zip

[asdine]

I don't think it's related to Go 1.8 but only to the version 0.6.56. The bug occured the moment i upgraded

[ramya-rao-a]

Hello people,

just saw this.
Thanks for reporting.

Most likely culprit is #864

Will send out a fix soon

[ramya-rao-a]

Looking at all the error messages posted here, it looks like a classic off by 1 error.
dataAccess -> ataAccess
code -> ode

But unfortunately, neither did I see this error while testing, nor can I see it now in any of my Go projects.

All of my Go project paths are of the form $GOPATH/src/github.com/somebody/someproject and I cant see this error in any of them.

So I created another project right under $GOPATH/src like @a57571735. Can't repro the bug then either :(

@a57571735 @nezorflame Since you have local dev env available for the Go extension, can you help me debug this issue? You need to put a breakpoint at https://github.com/Microsoft/vscode-go/blob/master/src/goCheck.ts#L167 and see what values you are getting for currentGoWorkspace and importPath variables

[nezorflame]

@ramya-rao-a sure, in a couple of minutes (on the road right now)

[ramya-rao-a]

@a57571735 @asdine @nezorflame @ansencumt
Can you share some details about your GOPATH?

• Is your GOPATH set to multiple workspaces
• Are you using the go.gopath setting to override the GOPATH env variable
• Do you have go.inferGopath set to true ?
• Can you run the command Go: Current GOPATH and see if that looks right to you?

[nezorflame]

@ramya-rao-a

• yeah (set in .bash_profile: GOPATH="${GOPATH1}:${GOPATH2}:${GOPATH3}")
• no
• no
• seems OK

the funny thing is that if I create an empty folder in a folder path it tries to find, the error goes away.
it definitely has something to do with the project name.

[ramya-rao-a]

Alright, found the issue.

Commited the fix: d417fd6

Update 0.6.57 is out.

This issue only affects those who have multiple GOPATHs, and the Go project being worked on is not the first one among the multiple GOPATHs and the right GOPATH is shorter in length than the first GOPATH.

I know, thats a mouthful. And quite silly. I apologize for not testing multiple GOPATHs from my side.

Happy Coding!

[nezorflame]

@ramya-rao-a can confirm that it's fixed now (built from the latest comment).

[ramya-rao-a]

Thanks @nezorflame! The update is out as well.

[AaronReboot]

Hi, I was experiencing the issue described in this issue with 0.6.56. I just updated to 0.6.57 and there's still a problem:

It's now reporting "cannot import absolute path" at the top of all my package names

[ramya-rao-a]

@AaronReboot Can you share the build output from the output channel?

[ramya-rao-a]

@AaronReboot Make sure that the project you have opened is under the GOPATH that you get by running the command Go: Current GOPATH

[AaronReboot]

Sure thing. Here's my build output:

Finished running tool: /usr/local/go/bin/go build -i -o /var/folders/n_/7lfk4kw11hg0q83fy9kqc8jr0000gn/T/go-code-check -tags "" /Users/aaron/code/LLAPI
can't load package: package /Users/aaron/code/LLAPI: import "/Users/aaron/code/LLAPI": cannot import absolute path


Finished running tool: /usr/local/go/bin/go tool vet /Users/aaron/code/LLAPI/balance.go```

And here's my GOPATH
`Current GOPATH: /Users/aaron/code`

[ramya-rao-a]

Is there any reason, your project is directly under $GOPATH and not $GOPATH/src?

[AaronReboot]

It's just how things are organized at the firm I'm working for. It removes some of the complications with deploying App Engine projects.

I'd like to note there's been no difficulty with this simplified path structure prior to 0.6.56

[ramya-rao-a]

In 0.6.56 we pass the import path of the current package to go build

And to find the import path we assume that the current file is under $GOPATH/src
If we can't find the import path this way, then the path to the current directory is used (which is wrong, causing the error you are seeing, we should have used ., we will fix that soon)

[liaoya]

I met the same problem on both my Linux and Windows VSCode 1.10.2 and Go 0.6.57. There is only one folder in my GOPATH. I also move the code to src and has the same problem.

The following is output on my Windows.
file: 'file:///d%3A/temp/gopl/src/helloworld/helloworld.go'
severity: 'Error'
message: 'can't load package: package d:/temp/gopl/src/helloworld: cannot find package "d:/temp/gopl/src/helloworld" in any of:
C:\tools\go\src\d:\temp\gopl\src\helloworld (from $GOROOT)
c:\opt\gopath\src\d:\temp\gopl\src\helloworld (from $GOPATH)
'
at: '1,1'
source: ''

[ramya-rao-a]

Since I am not able to repro, can you uninstall the Go extension you have, and install it using the Go-0.6.58.vsix to confirm if the fix works for you?

• Uninstall Go extension
• Download the vsix file Go-0.6.58.vsix
• Run code --install-extension Go-0.5.58.vsix from the location where you downloaded the file

[ramya-rao-a]

@liaoya Please use the workaround above, that should fix the issue for you.

Also, I am curious about your set up. Do you have multiple GOPATHs set?
You are trying to build d:/temp/gopl/src/helloworld from which I am assuming d:/temp/gopl is your GOPATH. Can you run the command Go: Current GOPATH and share the result?

[liaoya]

The following is output of "go env" about gopath
set GOPATH=c:\opt\gopath
I use 0.6.58 in issue #895, and it works as before.

I will not put the workspace in environment variable gopath and there's one item in gopath which store third party library and tool.

I'm just a beginner of Go. Thank you very much for the wonderful extension.

[AaronReboot]

Hi. I'm happy to report that everything is fixed here too after manually installing 0.6.58!

[asdine]

Me too ! 👍

[lzelevinsky]

I had the same problem as others with 0.6.57. I have a single simple GOPATH.
Manually updating to 0.6.58 worked for me as well.

[gevg]

Me too ! 👍

[ramya-rao-a]

I just released an update (0.6.59) yesterday which has the fix