Open jgabriel98 opened 1 year ago
Same phenomenon occurs too in my settings. (|WSL hosted files| <----> |remote-ssh|)
VS Code version: 1.79.2 (system setup) Windows Version: Windows 11 22H2 (OS Build 22621.1848)
any updates or hints on this?
I am seeing the same problem when trying to copy a file from one explorer that's connected to, say host X, to another explorer window connected to host Y.
I'm experiencing the same issue even after adding wsl.localhost as an Allowed UNCHosts in settings, and reloading the window.
That message pops up for me as well....
I'm experiencing the same issue even after adding wsl.localhost as an Allowed UNCHosts in settings, and reloading the window.
That message pops up for me as well....
i confirm the exact same
@lramos15 any updates on this?
any solution?
I am experiencing this as well. Would be nice to be able to use VS Code to move files instead of having another SFTP software to install and use.
any solution?
@ErnestoR2 I gave up a long time ago
It stopped to work for me just now, when i tried to copy the path from the file i saw it wasn't adding the wsl path for the folders in it. So I extracted the images from zip with it's wsl full path and it worked, try to add \wsl.localhost\Ubuntu\
Does this issue occur when you try this locally?: No* (see note at end of Bug Description)
Bug Description
Cannot copy (dragp & drop) files from WSL container to remote-ssh on vscode.
Error
"The dropped file could not be accessed for import."
shows after trying to copy file from WSL container (on file explorer) to remote-ssh (on vscode).Note: drap & drop from host local file to remote-ssh works! It seems the problem is with |WSL hosted files| <----> |remote-ssh|
Steps to Reproduce:
setup:
Reproducing bug:
"The dropped file could not be accessed for import."