-
Notifications
You must be signed in to change notification settings - Fork 351
ESLint with SafeQL crashes on Windows with error code 3221226505 #1900
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
Comments
I cloned the repository but running eslint (even in the terminal) already fails with:
|
@dbaeumer , thank you for cloning the repository. I’ve updated the forked repo to include an |
@ProchaLu what kind of steps. After pulling I still get exceptions that the environment can't be read. I would also like to ask that you look into providing me with a GitHub repository with a minimal setup to reproduce this. The repository you gave me requires quite some setup and it will make it hard to track down the problem. |
@dbaeumer, I was not able to create a small repro because this issue is Windows related and I am using macOS. In the last day we narrowed the issue down and this issue seems to be coming from SafeQL and
and those issues cause crashes on Windows with exit code 127:
This also caused crashes in the editor. I will report this in a new issue for SafeQL. |
@ProchaLu thanks for letting me know. I will close the issue. Please ping if you thing there is anything that needs to be done in the extension itself. |
Uh oh!
There was an error while loading. Please reload this page.
In the Next.js forked repository, ESLint crashes frequently on Windows. Specifically, it crashed five times in the last three minutes.
Also when running ESLint in the terminal, ESLint doesn't report any issues.
Steps to Reproduce on Windows
cd finalpro
pnpm install
$ pnpm eslint . --max-warnings 0
Expected Behavior
ESLint should run without crashing and should report any linting issues found in the project files.
Actual Behavior
ESLint crashes with error code 3221226505 and does not report any linting issues.
Additional Information
var a = 1;
do not cause ESLint to report any issues on WindowsIs there anything else I can check or any additional information needed to troubleshoot this issue?
The text was updated successfully, but these errors were encountered: