Windows + [email protected]: SafeQL crashes with error code 127, error code 3221226505

[ProchaLu]

Describe the bug
SafeQL throws wrong errors with [email protected] on Windows and MacOS.

Issue also reported in VSCode ESlint repo:

• ESLint with SafeQL crashes on Windows with error code 3221226505 microsoft/vscode-eslint#1900

Misleading errors:

• incorrect table name (user instead of users)
• missing comma (should be after users.id)
• curly brackets instead of parentheses (after ON)

On macOS ESlint throws these errors:

➜  safeql-eslint-broken git:(main) ✗ pnpm eslint . --max-warnings 0
(node:48991) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Warning: React version was set to "detect" in eslint-plugin-react settings, but the "react" package is not installed. Assuming latest React version for linting.
Pages directory cannot be found at /Users/lukas/Documents/UpLeveled/safeql-eslint-broken/pages or /Users/lukas/Documents/UpLeveled/safeql-eslint-broken/src/pages. If using a custom path, please configure with the `no-html-link-for-pages` rule in your eslint config file.

/Users/lukas/Documents/UpLeveled/safeql-eslint-broken/database.ts
  13:0  error  Invalid Query: Error: syntax error at or near "."  @ts-safeql/check-sql
  35:0  error  Invalid Query: Error: syntax error at or near "{"  @ts-safeql/check-sql

On Windows ESlint throws an error code 127 "command not found"

$ pnpm eslint . --max-warnings 0
(node:11440) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
$ echo $?
127

On Windows with these issues, the ESLint VSCode extension crashes after 5 times in 3 minutes

To Reproduce

1. Clone repo git clone https://github.com/ProchaLu/safeql-eslint-broken
2. set .env variables
3. migrate up
4. Check the code and errors in the database.ts file

Expected behavior
The expected behavior would be that SafeQL throws correct errors.

• incorrect table name (user instead of users)

• missing comma (should be after users.id)
  The error should lead to the missing comma.

export async function getUsers1() {
  return await sql<Users[]>`
    SELECT
      users.id,
      users.name
    FROM
      users
  `;
}

• curly brackets instead of parentheses (after ON)
  The error should lead to the wrong use of curly brackets.

export const getUsers3 = async (sessionToken: string) => {
  const users = await sql<{ id: number; name: string }[]>`
    SELECT
      users.*
    FROM
      users
      INNER JOIN sessions ON (
        sessions.token = ${sessionToken}
        AND expiry_timestamp > now()
      )
  `;
  return users;
};

OS: Windows
PostgreSQL version 15.7

[karlhorky]

Using the research strategy from issue #261, I've decoded the error code 3221226505 to the hex code 0xC0000409, which is more googlable.

How do you diagnose the exception code 0xc0000409 on Windows? | Stack Overflow

0xc0000409 means STATUS_STACK_BUFFER_OVERRUN.

In other words, something in your program is writing past the current stack frame, corrupting data on the stack. The program has detected this and rather than let it continue, has thrown an exception.

[karlhorky]

I've also reported this in a new libpg-query issue, to surface the crashes over there too:

• Windows fatal exceptions 0xC0000409 and 0xE06D7363 with [email protected] via SafeQL launchql/libpg-query-node#81

[ProchaLu]

I was able to reproduce this in a GitHub Actions workflow for Windows. Running eslint . exits with 127 and no details, but using a script to capture the real exit code shows 3221226505 (0xC0000409 STATUS_STACK_BUFFER_OVERRUN), confirming the crash.

• https://github.com/ProchaLu/eslint-libpq-query-issue

Running pnpm eslint . --max-warnings 0 in GitHub Actions results in this error:

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 pnpm eslint . directly. The script runs ESLint using Node and captures the actual exit code instead of letting it be masked by the CLI wrapper. This surfaced the real error (0xC0000409), which suggests that SafeQL may not be handling libpg-query crashes properly.

[Newbie012]

which suggests that SafeQL may not be handling libpg-query crashes properly.

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 libpg-query to pg-query-emscripten which is a port of libpg_query in wasm. I even used it in pg-query-ast-explorer and it looks great, but I haven't tested the performance.