microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.67k stars 291 forks source link

Error: "Handler ready set!" #5096

Open kingsimba opened 3 years ago

kingsimba commented 3 years ago

I believe I'm experiencing the same thing as #4705

Steps to Reproduce:

  1. Open WSL. cd ax-platform-control
  2. Open VS Code with code .

image

Workaround:

Rename "ax-platform-control" to "ax-platform-control-2". It will be OK for several days. Then the same problem happen. I'll have to rename it to "ax-platform-control-3".

Additional Info:

  1. Rebooting WSL or the host windows PC doesn't help.
  2. The problem only affects this specific folder. Deleting it and re-clone the project doesn't help. But renaming it will help. Renaming it back, the problem persists. So I think it has something to do with the cache on Windows AppData.
kingsimba commented 3 years ago

This is really annoying. I've reached ax-platform-control-8 in two days and keep renaming!

bamurtaugh commented 3 years ago

Hi @kingsimba, is this project stored any differently than other files/folders with which you've worked in Remote-WSL? Is it on the WSL file system or the Windows file system and mounted into WSL?

kingsimba commented 3 years ago

Hi @kingsimba, is this project stored any differently than other files/folders with which you've worked in Remote-WSL? Is it on the WSL file system or the Windows file system and mounted into WSL?

It's in the WSL2 file system. I don't think there is anything special about the affected projects.

Remove everything under %AppData%\Code seems to resolve the problem temporarily, before it happens again.

kingsimba commented 3 years ago

I nailed it down to %AppData%\Code\User\workspaceStorage\87089cfaff1a00c2b0841546fe40aee5. After deleting this folder. The problem is gone.

The problematic data is uploaded to https://github.com/kingsimba/vscode-remote-problem