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

Build fails with spawn EINVAL #68

Closed
derevnjuk opened this issue Apr 15, 2024 · 2 comments · Fixed by #69
Closed

Build fails with spawn EINVAL #68

derevnjuk opened this issue Apr 15, 2024 · 2 comments · Fixed by #69

Comments

@derevnjuk
Copy link
Contributor

derevnjuk commented Apr 15, 2024

Environment

  • Node.js Version: 18, 20
  • Platform: Windows x86

Description
The build process fails with an EINVAL error during the spawn operation in node-gyp-build. This issue seems to affect only Windows x86 configurations. A similar problem has been reported in prebuildify: prebuild/prebuildify#83.

Steps to Reproduce

  1. Run the node-gyp-build in a Windows x86 environment using Node.js versions 18 or 20.
  2. Observe the failure in the build process.

Expected Behavior
The build should complete without errors.

Actual Behavior
The build process fails and outputs the following error:

> node-gyp-build

node:internal/child_process:421
    throw new ErrnoException(err, 'spawn');
    ^

Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:[11](https://github.com/NeuraLegion/node-raw-socket/actions/runs/8686906219/job/23819333405#step:4:12))
    at Object.spawn (node:child_process:761:9)
    at build (D:\a\node-raw-socket\node-raw-socket\node_modules\node-gyp-build\bin.js:30:8)
    at preinstall (D:\a\node-raw-socket\node-raw-socket\node_modules\node-gyp-build\bin.js:39:32)
    at D:\a\node-raw-socket\node-raw-socket\node_modules\node-gyp-build\bin.js:11:7
    at ChildProcess.exithandler (node:child_process:430:5)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1105:[16](https://github.com/NeuraLegion/node-raw-socket/actions/runs/8686906219/job/23819333405#step:4:17))
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  errno: -4071,
  code: 'EINVAL',
  syscall: 'spawn'
}

derevnjuk added a commit to derevnjuk/node-gyp-build that referenced this issue Apr 15, 2024
derevnjuk added a commit to derevnjuk/node-gyp-build that referenced this issue Apr 15, 2024
derevnjuk added a commit to derevnjuk/node-gyp-build that referenced this issue Apr 16, 2024
csett86 added a commit to jitsi/jitsi-meet-electron-sdk that referenced this issue Apr 21, 2024
@derevnjuk
Copy link
Contributor Author

@mafintosh, do you have any updates on this? Could you please review the PR?

@lyswhut
Copy link

lyswhut commented Apr 27, 2024

Same problem.
This is related to the security repair of Node: nodejs/node#52681

mafintosh pushed a commit that referenced this issue May 2, 2024
facebook-github-bot pushed a commit to WhatsApp/tree-sitter-erlang that referenced this issue Feb 14, 2025
Summary:
The CI issue on Windows was caused by a vulnerability. This was fixed in:

* [`prebuildify`](prebuild/node-gyp-build#68) 6.0.1
* [`tree-sitter`](tree-sitter/node-tree-sitter@4017cfe) 0.22.2

Bump the dependencies to include the respective fixes.

I am not sure if the Tree Sitter version has to be kept in sync with the one in `Cargo.toml`, so please advise. Also, I run:
```
make
make deps
make gen
```
To propagate the bump, not sure if more is needed.

Reviewed By: alanz

Differential Revision: D69656300

fbshipit-source-id: f73d873b510b9532f44dd7ee88028576a75db8d1
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

Successfully merging a pull request may close this issue.

2 participants