Project Errors never show up

Hi there Louis Brauer ! 

Thank you for your report. Could you please elaborate more on the issue you are having? I'd like to ask you to provide the following:

1. A screenshot illustrating what you see when you open the Project Errors tab.
2. Your IDE logs (Help | Collect Logs and Diagnostic Data). You can attach them here to keep them private - https://uploads.jetbrains.com/ . Please make sure to send us the upload ID so we could check them.
3. Could you please tell me what errors do you expect to see in the tab, if any? This will help us with the investigation of the issue.
4. Finally, if possible, please share the project files with us using which you are able to stably reproduce the issue.

Thank you and I hope to hear from you soon.

For some time, compilation errors for go files other than the current file do not show up. You can see them when performing go build ./…

The workflow is very long as you have to go back and forth between command line and edit each file.  The Problems→Project Errors window just shows an “Inspect Code..” button which is really only for coverage and other features.

Hi Phil,

Thank you for the question. Can you provide an example of the project using which you're able to reproduce the problem? Please also make a video or screenshots to illustrate how you run the build. I'd assume this might be expected as the compiler stops once it hits the first error as other errors might appear or not depending on the compilation in the previous steps. 

Also, do you mean you see multiple errors when running go build ./… in the terminal but not when you try to run the application int he IDE, or did I misunderstand this part?

Thank you!

It is happening with every project which leads me to believe it might be an IDE setting or corruption issue.  See screen shot attached.

In it you’ll see the file tab shows 4 errors, meanwhile the Project Errors tab shows “Inspect Code”. Clicking on it brings up things like code style, quality etc.

It used to be really helpful after a refactoring to have a list of build failures.  Right now, I have to execute go build ./… to look for build errors and go back and forth.

It used to be that the auto build featues of the IDE would report errors on more than just the current file.

I see. Thank you for the details. Can you please check what inspection profile you have selected when pressing the ‘Inspect Code’ button in the Project Errors screen?

Please try using the default one - it seems to correctly identify the errors in the whole project on my end. Please let me know if this is what you've been looking for.

With the recent release 2024.2.3 the problem still persists. I've several errors in my project and when I open it with GoLand, none of them are shown in the Problem area:

I'm not sure if I misunderstand how GoLand works, but I would expect that it has similar capabilities than other editors/IDEs that use gopls and continuously display any errors that occur while editing files in the project?

It used to be the project tab was the same as the file tab except it showed build errors for the entire project and nothing else. The current project tab does code analysis which isn’t that useful for dealing with refactoring issues. 

I did try to play with the Analyze function and it does not report errors.  To test, I started with a brand new mac and a brand new GoLand install.  I went into the analyze code function and instead of taking the default I looked through the items and deselected everything except for Go.   Nothing in the go analysis reports basic bugs.  Never-the-less, I intentionally place errors in multiple files and ran the analysis.  The errors aren't reported in the Project tab.  I get lots of “weak” warnings, but at the top the list should be build errors.  

As I think we've been trying to say, “Project Errors" is not showing project errors, but “Code Analysis” which is a very very different thing.

Agree. Not showing the actual project errors while refactoring renders GoLand completely unusable for me right now. I hope JetBrains will find a way to make this happen again.

Ah, I see. Sorry for my confusion. Indeed, we have a feature request to change the behavior of this window (or add a different one to show the errors in one place) listed here - GO-4618. I suggest you follow this case to get updated should there be any developments. Please note we can't guarantee any changes here, but I definitely understand how this might be useful if added, and your votes will help us better evaluate the demand for such functionality to be implemented.

I am having this exact same issue.  It makes Intellij almost unusable for Go coding.  Java software development works as expected.

Hi Luke,

Could you please make some screenshots to illustrate how things look like when using Java? I'll make sure to discuss this with the team internally and this will help us better understand how things should look like.

Thank you!

Example code is below.  In this very simple example, I have an Employee struct that implements Person.  At first I coded the example *without* the `Email` method on Person.  This code compiles and runs as expected.

If I add the `Email` method to the Person interface, there *should* be errors immediately shown in main.go and employee.go because the code will fail to compile.   VSCode will show the project wide-failures automatically.

When I implemented a similar code in Java, Intellij immediately displayed the problem in Person.java interface definition as `1 related problem` with a clickable link that navigates to Employee.java.

In this scenario, I still prefer the VSCode solution to show project-wide build errors compared to the experience in Intellij.  However, at least for Java, Intellij does point out that there is an error in the file that is being edited.

main.go

package main

import (
	"fmt"
)

func main() {
	var p Person
	emp := Employee{"Sam", 25}
	// Verifies assignment
	p = emp
	fmt.Printf("Name: %s, Age: %d\n", p.Name(), p.Age())
}

person.go

package main

type Person interface {
	Name() string
	Age() int
	Email() string // added later
}

employee.go

package main

// Employee implements the Person interface
var _ Person = Employee{}

type Employee struct {
	name string
	age  int
}

func (e Employee) Name() string {
	return e.name
}

func (e Employee) Age() int {
	return e.age
}

Luke Mauldin Thank you! This illustrates the problem perfectly - the errors won't show up unless you change the focus to the main.go or employee.go files, and using the Project Errors screen doesn't highlight the errors automatically indeed, unless Inspect Code is used (which can be not perfect if you're continuously refactoring the code). 

I added this internally to back up the necessity of implementing the feature raised here, GO-4618. Can't guarantee any changes, but this is on the team's radar.

Thank you, and sorry for any inconvenience.

I'm bummed that this bug doesn't seem to have any weight.  I've been really enjoying a lot of the features of Goland but the lack of quick feedback from the IDE regarding compile errors makes buying the license a non-starter.  That's just too central to my workflow and it's something that the free editors just do so well.

If it gets fixed I will be interested in re-evaluating whether to license Goland.

I have the same bug on Mac.

The same thing happens in PhpStorm on Mac. The problems are shown in the File tab, if im focused on the file. On the Project tab however, no errors are found. If i inspect the code on lets say uncommited files, there errors are also found.

 

i have the same issue as well. Build #GO-241.19072.18, built on August 8, 2024
Runtime version: 17.0.11+1-b1207.30 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

i updated my build to this Build #GO-243.23654.166, built on January 23, 2025
and it worked. GoLand 2024.3.2.1

Nope, not for me with the same build. Not even with 2025.1 EAP.

Could you perhaps share a screenshot?

Same problem here, on MacOS. Project window doesn't show compilation errors until unless I go to “problems” > “project errors”. Then I execute it and the project window shows the errors. Really annoying behavior. Unfortunately I can't share a screenshot due to sensitive info. This appears to be a recent behavior here. Updated from 2024.3.1 to 2024.3.3 last night.

GoLand 2024.3.3
Build #GO-243.24978.59, built on February 13, 2025
Runtime version: 21.0.6+8-b631.39 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.3.1
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation

 

Same issue here, I am having to run code analysis when I want to check for compilation errors on my project. VSCode does this in real time, if I rename a type in one file, I will see errors across the entire project instantly where that type is referenced. In Goland I have to run a full project analysis which is not going to work. 

I like Goland over VSCode for a lot of other reasons, but this is definitely a blocker for me to switch to Goland for work, so I won't be at this time. 

GoLand 2024.3.4
Build #GO-243.25659.52, built on February 27, 2025
Licensed to Joseph Ferrero
Subscription is active until March 27, 2025.
Evaluation purpose only.
Runtime version: 21.0.6+8-b631.39 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.lwawt.macosx.LWCToolkit
macOS 15.3.1
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 2048M
Cores: 10
Metal Rendering is ON
Registry:
 ide.completion.variant.limit=500
 suggest.all.run.configurations.from.context=FALSE
 ide.experimental.ui=true
 terminal.new.ui=true
Non-Bundled Plugins:
 com.github.dinbtechit.vscodetheme (1.11.0)
 

It's concerning that this issue persists in GoLand. Obviously nobody at JetBrains is using GoLand themselves, so no GoLand licenses for our team. 

I have a license but I don't use Goland because of this problem.

This is happening to me too.