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 w/ WSL Prevents folder from being moved/renamed despite all files being closed #112764

Closed
apham-sy opened this issue Dec 17, 2020 · 2 comments
Assignees

Comments

@apham-sy
Copy link

apham-sy commented Dec 17, 2020

  • VSCode Version:1 .
  • OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

  1. Open VSCode w/ WSL
  2. Open a file in a subdirectory. E.g. /tmp/testfolder/file.py
  3. Close that file tab (while keeping vscode still open)
  4. Attempt to move that folder through windows explorer or vscode
  5. You should get
    Error: EACCES: permission denied, rename '/tmp/testfolder' -> '/newlocation/testfolder/'
    If you attempt to move with windows you will get
    image

It looks like vscode holds onto the lock (if this is correct) of the parent folder of a modified file despite it being closed in WSL. This is not a problem when not using Remote - WSL.

The problem occurs when you rename the folder as well.

Maybe related to microsoft/WSL#1529

Does this issue occur when all extensions are disabled?: Yes/No
Remote - WSL is required to open the remote window.

@apham-sy apham-sy changed the title VSCode w/ WSL Prevents folder from being moved despite all files being closed VSCode w/ WSL Prevents folder from being moved/renamed despite all files being closed Dec 17, 2020
@isidorn
Copy link
Contributor

isidorn commented Dec 18, 2020

Assigning first to @aeschli because it is WSL related, and Explorer is not doing anything special here

@isidorn isidorn assigned aeschli and unassigned isidorn Dec 18, 2020
@aeschli
Copy link
Contributor

aeschli commented Dec 18, 2020

@aeschli aeschli closed this as completed Dec 18, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants