-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: gopls crash with vscode-go in remote development #39789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report! Pasting the stack trace here so it's easier to find:
/cc @heschik |
I spent some time poking around this bug. The path to the WSL folder has "wsl$". Somewhere in the callstack, it's converted to %24. However, net/url doesn't think "$" should be escaped. This inconsistency caused net/url to return an error and then span.URI.FileName calls panic. I wasn't able to figure out what code converts "$" to "%24". |
Thanks for looking into this! VS Code seems to over-escape characters in a number of cases, and I believe we already ran into this with |
The file URL is invalid in a new way: it only has two slashes. It should be I guess we can try to fix up this too. |
Change https://golang.org/cl/239743 mentions this issue: |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Ubuntu on WSL 2.
gopls-error.txt
go env
OutputWhat did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: