Thank you for filing a gopls issue! Please take a look at the Troubleshooting guide, and make sure that you have provided all of the relevant information here.

Seeing error messages like

[Error - 12:27:01 PM] 2020/05/05 12:27:01
	message="failed to load workspace packages, skipping diagnostics"
	error=github.com/sanity-io/gradient/pkg/search/elasticsearch/indexstate_test [github.com/sanity-io/gradient/pkg/search/elasticsearch/indexstate.test] has no metadata
	snapshot=244
	directory=file:///Users/alex/Projects/Sanity/gradient

which leads me to believe that this is a duplicate of #38878, which is in turn a duplicate of #38423 (and probably related to #38358).

Got it. It's pretty hard to understand what the cause of a bug is and therefore know if it's a dupe, sorry. As an aside, is there no way for gopls to report itself as broken so that things don't get stuck, and maybe an error message bubbles up to VSCode?

No worries - I appreciate you filing all of these issues with logs. We can probably use a window/showMessage when we start skipping diagnostics to make the error more visible to the user.

I just got the error again, after restarting gopls. In other words:

• git rebase, got conflict markers.
• Restarted gopls and even reloaded window a couple of times.
• Gopls reports same errors as top of this issue.

gopls.log.gz

I wasn't sure if the bug in the other issues related to new files appearing while gopls was running, or just changes in test files.

Thanks for the report. It looks like we're failing to load a package from a file, but we don't log any errors. I added a better error log in https://golang.org/cl/230315, so when that's merged it would be easier to figure out why this happens.

I suspect this is a dupe of the transitive invalidation bug?

Yes, probably true. Should be fixed in gopls/v0.4.4.