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.

I'm not able to reproduce this - this is the error I see:

What directory did you have open when you saw this? It's possible that if the file wasn't in the directory at the root of your workspace, then gopls didn't report diagnostics for it (something we will be fixing in gopls/v0.5.0).

If you still have the full logs for this, those would be helpful to see.

Hey @stamblerre, thanks for the quick response!

I'm not quite up on the lingo for what a VSCode Workspace means, but here's my project's directory structure. I opened it with code .

.
├── commands
│   ├── migrate
│   └── web
├── controllers
│   ├── pages
│   └── users
├── go.mod
├── go.sum
├── internal
│   ├── env
│   └── log
├── main.go
├── migrate
│   └── migrate.go
└── views
    └── pages

The file with the syntax error is migrate/migrate.go.

I'm sadly not able to reproduce this issue reliably and I don't have the logs anymore. If I open VSCode fresh, it does properly show the error:

What I can say is that over time, as I'm adding and deleting files, it eventually stops reporting. It sounds like 0.5.0 might provide a solution for this issue? 😬🙏

Also let me know if you need more from me or if you already know what the issue is. I can try and create a better reproduction.

Ah, ok so then it looks like your workspace is configured correctly and the diagnostics should be propagating. In the future when this happens, I'd suggest capturing detailed gopls logs (https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capturing-logs) so that we can see what sequence of edits led to this state.

The process of cache invalidations after adding and deleting files is not perfect yet, so it's likely that that was the cause. I will be adding more integration tests soon, so I'll retitle this issue to make sure I add a few cases for adding and deleting files.

Okay sounds good. Do I also need to enable trace logs or is the default log output detailed enough?

You'll want to add the -rpc.trace flag to go.languageServerFlags.

Note to self: Another case to add a regression test for is microsoft/vscode-go#3179 (comment).

Closing since I this appears to be addressed 🙌