-
Notifications
You must be signed in to change notification settings - Fork 310
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
Reveal in File Explorer feature won't work when using WSL2 remote #9037
Comments
Same issue here, reverting back works too. |
[FYI] |
I'm running into this issue right now. |
For any potential contributors looking to fix this, what codebases should we look into modifying to fix this issue, and how would we test that our changes worked? |
I released a fix in WSL extension version 0.81.8 |
This functionality seems to be working with |
Thank you! |
I also verified |
For those that see their WSL extension in VSCode has version v0.81.8 but "Reveal in File Explorer" still does not work, just do a reload of the VSCode and it should work. If the WSL the extension says "Reload required", you can click that as well. |
I am still having an issue, even with v0.81.8 and restarting VSCode. When I click "Reveal in File Explorer", file explorer opens, but it doesn't open to the correct folder. It always opens to the "Desktop" folder for some reason. |
It works for me on Ubuntu 22.04 LTS.
I have
What operating system are you using, and does the issue reoccur reliably, even after restarting your machine? |
I rebooted and it works. shrug I had rebooted just that morning. Who knows. |
VSCode Version: v0.81.5
Local OS Version: Windows 10 22H2 Build 19045.3516
Remote OS Version: WSL2 Ubuntu-22.04
Logs: No logs
Steps to Reproduce:
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No
As a side note, I reverted to the previous version v0.81.5 and it works pretty well, looks like the issue is with a bug in the latest patch that was released some hours ago.
The text was updated successfully, but these errors were encountered: