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

spago init does not work for Windows 10 #1312

Closed
Bruce-Hall-git opened this issue Jan 21, 2025 · 4 comments
Closed

spago init does not work for Windows 10 #1312

Bruce-Hall-git opened this issue Jan 21, 2025 · 4 comments

Comments

@Bruce-Hall-git
Copy link

I know that you made a fix recently to "solve" this issue for the latest version of Windows (Windows 11). Specifically, you merged your fixes for #1308 a few days ago. I tested your changes on a Windows 11 machine and, while they don't work for a 'git bash' environment, they do seem to work for a PowerShell environment.

However, your fix doesn't seem to solve the problem for Windows 10, for either 'git bash' or PowerShell. Here is the feedback from both environments under Windows 10:

git bash

spago init
file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48911
throw util.fromLeft(step3);
^

Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:753:9)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:83989:18
at runSync (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48568:21)
at run16 (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48761:25)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48777:23
at drain (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48595:9)
at Object.enqueue (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48613:11)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48771:31
at __do4 (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:86427:77) {
errno: -4071,
code: 'EINVAL',
syscall: 'spawn'
}

Node.js v23.3.0

PowerShell

spago init
file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48911
throw util.fromLeft(step3);
^

Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:753:9)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:83989:18
at runSync (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48568:21)
at run16 (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48761:25)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48777:23
at drain (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48595:9)
at Object.enqueue (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48613:11)
at file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:48771:31
at __do4 (file:///D:/Programs/nvm/v23.3.0/node_modules/spago/bin/bundle.js:86427:77) {
errno: -4071,
code: 'EINVAL',
syscall: 'spawn'
}

Node.js v23.3.0

I suppose one advantage here is that the failure seems to identical using both shell environments so perhaps at least the problem is independent of the shell used. Hopefully, that at least helps narrow the search for a fix/work-around.

@f-f f-f added the bug label Jan 22, 2025
@f-f
Copy link
Member

f-f commented Jan 22, 2025

Thanks for reporting @Bruce-Hall-git. Unfortunately I am out of my depth here, as I don't use Windows myself, and just applied the fix that was recommended by the Node report; I would appreciate if you (or anyone else affected by this) could look into a proper fix for this!

@f-f
Copy link
Member

f-f commented Jan 23, 2025

@Bruce-Hall-git I just noticed that it seems like you used the released version of Spago - that did not include the recent fixes. I just released a new version 0.93.42, would be great if you could give it a try!

@Bruce-Hall-git
Copy link
Author

I just tried out version 0.93.42 on my Windows 10 machine and it works (under PowerShell). Thanks for fixing it!

@f-f
Copy link
Member

f-f commented Jan 23, 2025

You're welcome!

@f-f f-f closed this as completed Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants