Closed johnhwright closed 1 year ago
Same for WSL on Windows.
Hi guys.
Really appreciate you raising this issue. Unfortunately, it's a no-can-fix.
The underlying process is super filesystem intensive, and on virtual environments, using the VS Code virtual filesystem intensively at scale is super-slow. So, I could do it but you wouldn't be happy waiting 5-10 minutes for it to do its thing.
See closed issue 28
Hi Tom, thanks for the fast reply. I guess I just use a vs code instance inside of the wsl container only for this awesome extension 😊 .
Is your feature request related to a problem? Please describe. Not sure what's preventing it, but we do a lot of work over the vscode's remote development and sadly this extension doesn't work.
Describe the solution you'd like Currently just does nothing and prints:
to the extension log.
Describe alternatives you've considered Have to remote into the machine hosting the code and run it in a VS code instance locally...
Additional context