Change https://golang.org/cl/291192 mentions this issue: internal/lsp: refactor go command error handling

That CL was not supposed to close this issue, but it might be worth checking if it incidentally fixed it.

Doesn't seem like it, unfortunately. I can still reproduce the original issue.

Thanks for confirming, I'll take a look when I get a chance.

I'm afraid I can't reproduce it, even with experimentalWorkspaceModule. I get a diagnostic on the appropriate line of the go.mod, as well as an "Error loading workspace" status message. Can you double-check that you're using a version with that CL included and upload a log? Sorry for the trouble.

@heschik, yes, I can still reproduce it. The --logfile option didn't work for me—the files turned out empty every time for some reason—, so I decided to instead use the “nuclear” option and just wget -E -k -r the debug output and then compress and attach them.

• good.tar.gz
• bad.tar.gz

Build info from info.html:

golang.org/x/tools/gopls master
    golang.org/x/tools/gopls@v0.0.0-20210218195900-9eb353543b38 h1:vmOMMCKj9UAuhJ61XbbL2YWVaSREl71VJi+goBsaDZo=
    github.com/BurntSushi/toml@v0.3.1 h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ=
    github.com/google/go-cmp@v0.5.4 h1:L8R9j+yAqZuZjsqh/z+F1NCffTKKLShY6zXTItVIZ8M=
    github.com/sergi/go-diff@v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
    golang.org/x/mod@v0.4.1 h1:Kvvh58BN8Y9/lBi7hTekvtMpm07eUZ0ck5pRHpsMWrY=
    golang.org/x/sync@v0.0.0-20201020160332-67f06af15bc9 h1:SQFwaSi55rU7vdNs9Yr0Z324VNlrF+0wMqRXT4St8ck=
    golang.org/x/sys@v0.0.0-20210124154548-22da62e12c0c h1:VwygUrnw9jn88c4u8GD3rZQbqrP/tgas88tPUbBxQrk=
    golang.org/x/tools@v0.1.1-0.20210218195900-9eb353543b38 h1:AOnqnOc/zrpEP0Jf7fGER9N5n4xWmoQg7FvdiH78xeQ=
    golang.org/x/xerrors@v0.0.0-20200804184101-5ec99f83aff1 h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE=
    honnef.co/go/tools@v0.2.0-0.dev.0.20210217134301-16f40c10b7a4 h1:5KJ5c2KSzEy2O2ANwZCbZEEyicSDg7yXvfrlZT6dMAI=
    mvdan.cc/gofumpt@v0.1.0 h1:hsVv+Y9UsZ/mFZTxJZuHVI6shSQCtzZ11h1JEFPAZLw=
    mvdan.cc/xurls/v2@v2.2.0 h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A=

Please let me know if there is any other useful info I can provide.

Interesting approach. Happened to work here. From bad/client/1.html:

/tmp/gomod/go.mod:
   (0:0-0:0)"unknown directive: package"(source:"syntax",code:"",severity:Error,snapshot:2,type:FromSource)
   (0:0-0:0)"/tmp/gomod/go.mod:1: unknown directive: package"(source:"go list",code:"",severity:Error,snapshot:2,type:FromSource)

So I'm not quite sure what to tell you. It appears we're generating errors at least to some extent, but they're not showing up in the client?

@findleyr, can you shed any light on this since you know vim stuff?

@heschik, I've done some more digging, and apparently gopls sends a window/logMessage request rather than a more appropriate window/showMessage one. In the verbose Neovim logs:

[ DEBUG ] 2021-02-19T00:47:46+0300 ] /usr/share/nvim/runtime/lua/vim/lsp.lua:500 ]	"notification"	"window/logMessage"	{  message = "2021/02/19 00:47:44 errors loading workspace: /tmp/gomod/go.mod:1: unknown directive: package\n\tsnapshot=1\n\tdirectory=file:///tmp/gomod\n",  type = 1}
[ DEBUG ] 2021-02-19T00:47:46+0300 ] /usr/share/nvim/runtime/lua/vim/lsp/handlers.lua:407 ]	"default_handler"	"window/logMessage"	{  client_id = 1,  params = {    message = "2021/02/19 00:47:44 errors loading workspace: /tmp/gomod/go.mod:1: unknown directive: package\n\tsnapshot=1\n\tdirectory=file:///tmp/gomod\n",    type = 1  }}

From what I can tell, including this message by @stamblerre, window/logMessage is for logging whilewindow/showMessage is for actually showing a message to the user. Am I wrong here?

That is debug logging, not user-facing. showMessage is a modal dialog and definitely not appropriate here. gopls is publishing user-facing diagnostics that your editor is not showing; you can see them if you enable rpc.trace and in the debug page I mentioned above.

It seems like you are correct. Maybe some kind of an issue with how Neovim handles diagnostics from buffers that aren't loaded and files that aren't open. I'm going to close this issue and keep digging. Sorry for the noise.