Workspace library folder locked

[FlashHit]

but the issue is that when you specify a workspace library folder for his extension, it locks that directory. So if you want to delete or move the directory, you can't

rejected promise not handled within 1 second: Error: EBUSY: resource busy or locked, rmdir 'e:\code\vscode-lua-testmod\.vu\intermediate\Shared'
c:\Users\scrap\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js:5
stack trace: Error: EBUSY: resource busy or locked, rmdir 'e:\code\vscode-lua-testmod\.vu\intermediate\Shared'
c:\Users\scrap\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js:5

[Imposter]

Just want to step in here and add some details to set the context. I maintain the Vua extension which utilizes your Lua extension under the hood.

We utilize a workspace with three folders which contain separate Lua code (and as such, each have an instance of the language server running). The problem occurs when we set a Workspace Library in the vscode/settings.json in the individual folders. The Vua extension has the ability to update the libraries while VS code is running and deletes/renames directories that are added to Lua.workspace.library. I recall this working fine a few months ago, but now when we delete the workspace library while the language server is running, we get the error that @FlashHit shared above.

It seems the language server is locking workspace libraries which prevent us from modifying them.

[sumneko]

fixed by 9908df0