Robert Findley

I don't think we're going to make progress on root causing these, but we can perhaps add a retry.

I see the race in this test: the test may advance to applying code actions before changes are processed (because there is both a didChange and didSave notification being processed,...

Thanks for following up!

CC @suzmue @jamalc

2p: if we can avoid configuration, that would be better. Could this be the default behavior? What do other languages do?

It looks like this error comes from VS Code itself, so we're producing incorrect position information somewhere.

@thanm thanks for pointing that out. This could also be a tool somewhere in the `go test` stack mishandling the line directive (compare golang/go#55043). Needs investigation to see. Thanks for...

> Gopls only finds the references on package level, not on module level. FWIW, this is not what I observe, and is certainly not the intended behavior. Gopls should find...

No, find all references should consider all workspace packages. If you do not see this happening, it is either a bug or a misconfiguration (or both). If you had a...

> I don't really have a minimal reproducer, but I do have a workspace error, could that be related? Yes, that is almost certainly related. What is your workspace error?...