Skip to content
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

VSCode Remote WSL: unable to rename folder #208

Closed
eisber opened this issue May 7, 2019 · 5 comments · Fixed by microsoft/vscode#76009
Closed

VSCode Remote WSL: unable to rename folder #208

eisber opened this issue May 7, 2019 · 5 comments · Fixed by microsoft/vscode#76009
Assignees
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) wsl Issue in vscode-remote WSL
Milestone

Comments

@eisber
Copy link

eisber commented May 7, 2019

Issue Type: Bug

I tried to rename a folder with some files in it and it silently failed. When trying in the terminal inside VSCode, in WSL bash or Windows Explorer I get permission denied (another program accesses the folder).

Extension version: 0.32.0
VS Code version: Code - Insiders 1.34.0-insider (daf71423252a707b8e396e8afa8102b717f8213b, 2019-05-06T22:08:08.969Z)
OS version: Windows_NT x64 10.0.18362
Remote OS version: Linux x64 4.4.0-18362-Microsoft

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 15.93GB (3.50GB free)
Process Argv
Screen Reader no
VM 0%
Item Value
Remote WSL
OS Linux x64 4.4.0-18362-Microsoft
CPUs Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)
Memory (System) 15.93GB (3.48GB free)
VM 0%
@roblourens roblourens added the wsl Issue in vscode-remote WSL label May 8, 2019
@egamma egamma added upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) *duplicate Issue identified as a duplicate of another issue(s) labels May 8, 2019
@egamma
Copy link
Member

egamma commented May 8, 2019

Duplicate of microsoft/WSL#3395.

This will be addressed by WSL2!

@auchenberg
Copy link

Re-opening, as this is still an issue in WSL1 and we may need to address this until WSL2 ships.

@egamma
Copy link
Member

egamma commented May 27, 2019

@isidorn @aeschli can we provide an error message that tells the user that this is a WSL limitation when this happens in a WSL context.

@egamma egamma removed the *duplicate Issue identified as a duplicate of another issue(s) label May 27, 2019
@isidorn
Copy link

isidorn commented May 27, 2019

I think the issue here is that the error silently fails. Let me first look into if we can surface the error, and only then if we can provide a better one.

@aeschli
Copy link
Contributor

aeschli commented Jul 4, 2019

There's now a new setting to swich to polling and avoid the 'can not rename' probem.
See https://code.visualstudio.com/docs/remote/wsl#_i-see-eaccess-permission-denied-error-trying-to-rename-a-folder-in-the-open-workspace

@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) wsl Issue in vscode-remote WSL
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants