-
Notifications
You must be signed in to change notification settings - Fork 195
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
Error when Folder is in WSL 2 filesystem, opened over \\wsl$ #411
Comments
@SupunSam has the same error, see here: #398 (comment) |
Same environment(WSL2, Ubuntu/windows 11) and error here. Here is the full output:
@f00f, Have you found any work around about this error? |
Nope, no workaround yet. I'm using it in a side-project, so putting limited effort in this 😎 |
The file resolution is fixed in |
I have a gatsby project in my WSL 2 home in the linux file system, i.e. in
/home/f00f/my-project/
.For editing in VS Code I go to
\\wsl$\Ubuntu-20.04\home\f00f\my-project\
in Windows Explorer and then select "Open in VS Code" in the context menu.So code lives in linux fs, VS Code runs in Windows, linux fs is shared via network (which is a default WSL 2 feature, not configured by me).
When I enable the extension I get the following error message:
which is almost the correct path. Discovery finds the config file, but
normalize-path
inserver.ts : init()
changes the actual path and removes the first backslash. That changes the path from a network path to an absolute path on the current drive on Windows.Note: in a previous comment I wrote the path in the error message with forward slashes. I cannot reproduce whether it really had forward slashes at that time. Right now I see backslashes.
The text was updated successfully, but these errors were encountered: