Closed leguminosa closed 4 years ago
Thank you for the report!
/cc @heschik because I believe you looked into gitlens files at some point? Based on the crash, it looks like the entire workspace root is a gitlens file, though I don't really understand how that works.
yes it's true, when opening changes with previous revision, I accidentally pressed Explore Repository from Revision
and everytime my repo is in that "state" (older revisions), gopls
will panic.
The thing is, I don't know how to "undo" that state and return to normal state and from https://github.com/eamodio/vscode-gitlens/issues/997 the gitlens itself stated that you cannot return to normal state, thus gopls will stuck in its panic state right at the start of vscode running and renders it unusable.
It's a certainty that this gopls and gitlens have something ...
gitlens implements a custom file system provider using vscode's FileSystemProvider API on top of git.
Not sure how much go list
can handle the partial info.
There are other document schemes https://github.com/eamodio/vscode-gitlens/blob/master/src/constants.ts#L54 but I don't know how others interact with editors and potentially triggers requests to the language server.
Change https://golang.org/cl/244602 mentions this issue: internal/lsp: check URIs of all workspace folders
One way or another, I'm pretty sure this is fixed. Please comment if you disagree.
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.