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

Not working on RAM disk on Windows #1315

Closed
darky opened this issue Aug 12, 2021 · 3 comments
Closed

Not working on RAM disk on Windows #1315

darky opened this issue Aug 12, 2021 · 3 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@darky
Copy link

darky commented Aug 12, 2021

  1. Create RAM disk, for example, via imDisk
  2. Place project on RAM disk
  3. Open VSCode, add project to workspace

Error in ESLint extension logs: 👇

(node:8956) UnhandledPromiseRejectionWarning: Error: EISDIR: illegal operation on a directory, realpath 'E:\dsm\dsm-backend-stocks-front-api\src\services\subscriptions\services\SubscriptionEditService.ts'
at Function.realpathSync.native (fs.js:1787:3)
at Function.native (electron/js2c/asar_bundle.js:5:4607)
at c:\Users\OUT-Botvin-VV.vscode\extensions\dbaeumer.vscode-eslint-2.1.23\server\out\eslintServer.js:1:14495
at z (c:\Users\OUT-Botvin-VV.vscode\extensions\dbaeumer.vscode-eslint-2.1.23\server\out\eslintServer.js:1:14555)
at c:\Users\OUT-Botvin-VV.vscode\extensions\dbaeumer.vscode-eslint-2.1.23\server\out\eslintServer.js:1:16827
(node:8956) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 409)

@dbaeumer
Copy link
Member

Looks like a node problem to me. realPathSync comes from the node FS module. One thing you can try as a workaround is to use eslint.runtime setting to point to the latest node version. Might be fixed there.

@dbaeumer dbaeumer added the bug Issue identified by VS Code Team member as probable bug label Aug 16, 2021
@dbaeumer dbaeumer added this to the On Deck milestone Aug 16, 2021
@darky
Copy link
Author

darky commented Aug 16, 2021

Yep, seems it's node problem. Hope this will help:

nodejs/node#6861 (comment)

Thanks for proper aiming.

@darky darky closed this as completed Aug 16, 2021
@dbaeumer
Copy link
Member

You are welcome.

@dbaeumer dbaeumer removed this from the On Deck milestone Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants