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

don't lock the dprint executable when the LSP is running #88

Open
DetachHead opened this issue Jun 11, 2024 · 0 comments
Open

don't lock the dprint executable when the LSP is running #88

DetachHead opened this issue Jun 11, 2024 · 0 comments

Comments

@DetachHead
Copy link

when the dprint vscode extension is running, it locks the executable, which means the user can't update dprint while vscode is open:

npm error code EPERM
npm error syscall unlink
npm error path C:\Users\user\project\node_modules\dprint\dprint.exe
npm error errno -4048
npm error [Error: EPERM: operation not permitted, unlink 'C:\Users\user\project\node_modules\dprint\dprint.exe'] {
npm error   errno: -4048,
npm error   code: 'EPERM',
npm error   syscall: 'unlink',
npm error   path: 'C:\\Users\\user\\project\\node_modules\\dprint\\dprint.exe'
npm error }
npm error
npm error The operation was rejected by your operating system.
npm error It's possible that the file was already in use (by a text editor or antivirus),
npm error or that you lack permissions to access it.
npm error
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.

a possible solution could be for the extension to create a temporary copy of the executable and launch that instead, which is what my extension does to work around the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant