-
-
Notifications
You must be signed in to change notification settings - Fork 25
Windows + [email protected]
: SafeQL crashes with error code 127, error code 3221226505
#243
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
[email protected]
[email protected]
[email protected]
[email protected]
: SafeQL crashes with error code 127, error code 3221226505
Using the research strategy from issue #261, I've decoded the error code How do you diagnose the exception code 0xc0000409 on Windows? | Stack Overflow
|
I've also reported this in a new |
I was able to reproduce this in a GitHub Actions workflow for Windows. Running Running Error: Process completed with exit code 1. Running the script instead correctly captures the crash in this run: Run echo "Running eslint.mjs..."
Running eslint.mjs...
ESLint exited with code: 3221226505 (0xC0000409)
Error: Process completed with exit code 127. I can confirm this by running ESLint via a script instead of calling |
I might be wrong, but if I recall, even if I wrap the call to libpg-query with try/catch it will still fail since this error kill the entire process. I'm thinking of moving from |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
SafeQL throws wrong errors with
[email protected]
on Windows and MacOS.Issue also reported in VSCode ESlint repo:
Misleading errors:
user
instead ofusers
)users.id
)ON
)On macOS ESlint throws these errors:
On Windows ESlint throws an error code 127 "command not found"
On Windows with these issues, the ESLint VSCode extension crashes after 5 times in 3 minutes
To Reproduce
git clone https://github.com/ProchaLu/safeql-eslint-broken
.env
variablesExpected behavior
The expected behavior would be that SafeQL throws correct errors.
user
instead ofusers
)users.id
)The error should lead to the missing comma.
ON
)The error should lead to the wrong use of curly brackets.
OS: Windows
PostgreSQL version 15.7
The text was updated successfully, but these errors were encountered: