These error messages are removed in gopls at master, if you would like to update. However, master will likely not be as stable as the latest tagged version.

This error is a result of your editor showing the errors from the hover request to the user, so it might be worth filing that issue. Some editors, like VSCode, choose not show the errors from every request to the user.

@stamblerre I've included the commit hash in my original post. I am on master. I've just updated to 2756c524cc1ca1284d912b9c5ee3b0092ff4459b, which was committed recently, and the problem is still there.

Not sure “just ignore it” is a good strategy, but I will open an issue, if it wasn't already.

@stamblerre FWIW, I've replaced

return nil, fmt.Errorf("%s is not an identifier", fset.Position(pos))

with

return nil, nil

in internal/lsp/source/highlight.go, and it started working again.

Oh I'm sorry, I misunderstood - I had assumed that the error was with hover, not with document highlight.

In that case, this is definitely an error on the client side. We never return errors from document highlight (see here), they are only ever logged. The client should not show the user logged errors--the LSP specification has a specific window/showMessage request that is distinct from window/logMessage. I would suggest filing this issue on the vim-lsc repo.

You are very correct! Disabling logging with

let g:lsc_server_commands = {"go": {"command": "gopls serve", "log_level": -1}}

fixes the issue! Should I add info about this vim LSC implementation to the Wiki to prevent duplicates?

I think it might be best to file an issue with vim-lsc so that they can correct the problem, but as a temporary fix, adding a suggestion to the Wiki would also be helpful. Thanks!

Done. Thank you thrice: for helping me today, for your GopherCon Russia talk, and for gopls in general!

😄 And thank you for reporting this issue!