If you navigate to the Problems pane in VS Code or open your go.mod file, you should see diagnostics highlighting the error, along with suggested fixes. Clicking on those suggested fixes should resolve the problem. Does that work for you?

We have also been working on improving the error message, and I believe that will be addressed in an upcoming release.

@stamblerre , I am seeing this error after upgrading to gopls v0.6.5.

My VS code settings for gopls are:

   "gopls": {
        "build.experimentalWorkspaceModule": true,
        "build.expandWorkspaceToModule": true
    }

When I click on the light bulb and try to apply the suggested fix - which is to run go mod tidy and update go.sum nothing seems to happen.

I have run go mod tidy manually but nothing seems to happen.

The Error loading workspace message at the very bottom has a spinning icon next to it.

@samstride: Do you minding file a new issue so that we can discuss this separately? Also, please attach a gopls log to the issue. Information on how to capture logs can be found here.

@stamblerre , sure can do, however I am facing the exact same error message so do you want me to use a specific title for the new issue?

Any title is fine--you can also use the same title as this issue.

If you navigate to the Problems pane in VS Code or open your go.mod file, you should see diagnostics highlighting the error, along with suggested fixes. Clicking on those suggested fixes should resolve the problem. Does that work for you?

The problems pane is empty and there is no indication, which go.mod has the problem (which made it so confusing). As with @samstride the error indicator in the status line keeps spinning.

We have also been working on improving the error message, and I believe that will be addressed in an upcoming release.

If you think it's fixed then happy to close here.

I would not expect the Problems pane to be empty, so that's definitely still an issue. Can you please share your gopls logs? Information on how to capture them can be found here.

Good morning :) Here we go: gopls.txt.zip

Looks like the issue is in the github.com/andig/evcc module.

[Error - 7:26:53 PM] 2021/02/03 19:26:53 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- builtin github.com/andig/evcc/...]: exit status 1: go: updates to go.sum needed, disabled by -mod=readonly

	snapshot=0
	directory=/Users/andig/htdocs/evcc
	query=[builtin github.com/andig/evcc/...]
	packages=0

Do you still not see diagnostics on the go.mod file for that module? Does running go mod tidy in that module resolve the problem?

If not, it looks like that module is public--would you be willing to create a branch with a repro case for us to continue investigating?

Restarted vscode. This time, no spinner/error in status bar but message in problems view.

Do you still not see diagnostics on the go.mod file for that module?

No, gone. I'm wondering if the "sticky" errors are similar to #43821? Let's ignore that aspect and wait for go 1.16.

Now I'm getting output in the problem view. I still see an error there for a different module, however there's no fix available:

The problematic module here is outside the workspace (one level higher). Looking into this and running go mod tidy I see similar behaviour as #42250:

• I have simple testing ode in the parent folder for quick trial and errors
• I have added a go.mod there to avoid recursively going up the tree
• I still see that go mod update would go berserk and download the internet until it finally fails with a sirupsen/Logrus error

Long story short: I should not do this. I've moved the code from the parent folder to new and separate testing folder.

Shall we close here?