No buildable go source files after update Goland to EAP 19

Question

After I updated GoLand from EAP 18 to EAP 19 my imports are red and these errors occur in each file:

My $GOROOT and $GOPATH are the same as before. $GOROOT points to /usr/local/go. Files are buildable through shell but GoLand keep showing errors.

I am running GoLand on Mac OS with Go version go1.9.1 darwin/amd64:

GoLand (1.0 Preview) 1.0 EAP Build #GO-173.3727.24, built on November 16, 2017 GoLand EAP User Expiration date: December 16, 2017 JRE: 1.8.0_152-release-1024-b6 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Mac OS X 10.12.6

@EugeneLisitsky GOROOT= **usr/local/go** and GOPATH= **/Users/raca/GoglandProjects** which is my standard gopath — Ivan Aracki, Nov 17 '17 at 16:46
Looks like Goland has lost them or messed. Try to check them in goland glibal settings or project’s. — Eugene Lisitsky, Nov 17 '17 at 16:56
Are there non-test files in `flag` package? How the editor looks when you open them? — Alexander Zolotov, Nov 17 '17 at 17:30
@EugeneLisitsky there is no project settings anymore in GoLand, but global settings look OK. It also shows GOROOT and GOPATH are set correctly — Ivan Aracki, Nov 17 '17 at 18:25
@IvanAracki, unfortunately, this is not enough for diagnosis. Please file an issue at https://youtrack.jetbrains.com and attach logs (`Help | Compress logs and show in `) and a screenshot of the editor with opened `flag.go` file. — Alexander Zolotov, Nov 17 '17 at 20:46
@IvanAracki When I run anything with Goland, it shows me config in first lines. Like this: ```GOROOT=/usr/local/Cellar/go/1.9.2/libexec #gosetup GOPATH=/Users/e.lisitsky/go #gosetup /usr/local/Cellar/go/1.9.2/libexec/bin/go generate /Users/e.lisitsky/go/src/github.com/looplab/fsm/fsm.go #gosetup ``` . Could you check it pls? — Eugene Lisitsky, Nov 17 '17 at 20:55
Having the same problem on Ubuntu 17.10 after updating Goland — guilhebl, Nov 18 '17 at 09:14

score 11 · Accepted Answer · answered Nov 18 '17 at 11:59

11

It looks like indexes are corrupted. File | Invalidate Caches should help.

answered Nov 18 '17 at 11:59

Alexander Zolotov

694
5
11

1

doesn't help for me. Also have several projects that builds nicely but one of libs in import sections is underlined with red in IDE with the eroror that there is no buildable go files.. even with the fact that it is in vendor folder of each projects – Altenrion Jan 09 '18 at 10:04
Altenrion, then it makes sense to file an issue about it with diagnostic details such as IDE version, project structure and screenshots: https://youtrack.jetbrains.com – Alexander Zolotov Jan 09 '18 at 12:53

score 1 · Answer 2 · answered Apr 18 '18 at 10:01

1

When File | Invalidate Caches doesn't help, deleting the project and checking it out again does did the trick in my case.

answered Apr 18 '18 at 10:01

Macilias

3,279
2
31
43

score 1 · Answer 3 · answered Jun 12 '18 at 14:57

If invalidating caches does not fix the problem for you, it can also be that the package has build constraints that prevent it from being built on your system. I was attempting to import golang.org/x/sys/windows/svc while using Goland on a Mac and it took me a while to realize why Goland was saying it didn't have sources files when clearly it did. All the files in the golang.org/x/sys/windows/svc package are constrained to only build on Windows.

score 1 · Answer 4 · answered Jul 04 '18 at 16:37

1

One day I started to get this error on GoLand 2018.1

GOROOT & GOPATH where fine.

To fix that:

Opened File -> Settings -> Go -> GOPATH
Marked Index entire GOPATH

answered Jul 04 '18 at 16:37

michaelbn

7,393
3
33
46

score -1 · Answer 5 · answered May 25 '18 at 06:18

-1

Try these step:

close the goland IDE.
delete the .idea folder.
start the goland IDE.

answered May 25 '18 at 06:18

user9845013

11

No buildable go source files after update Goland to EAP 19

5 Answers5