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

Bug: ssc init fails to run on Windows with certain User Names #960

Open
jstarpl opened this issue Mar 14, 2024 · 1 comment
Open

Bug: ssc init fails to run on Windows with certain User Names #960

jstarpl opened this issue Mar 14, 2024 · 1 comment

Comments

@jstarpl
Copy link
Contributor

jstarpl commented Mar 14, 2024

What OS are you using (uname -a, or Windows version)?

Windows 11 23H2

What version Socket Runtime are you using?

0.5.4

What programming language are you using (C/C++/Go/Rust)?

N/A

What did you expect to see and what you saw instead?

I expected ssc init to scaffold the project.

Instead I got:

❯  ssc init
Error: spawn powershell.exe ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn powershell.exe',
  path: 'powershell.exe',
  spawnargs: [ '.\\bin\\install.ps1', '-fte:all' ]
}
@jstarpl
Copy link
Contributor Author

jstarpl commented Mar 14, 2024

I've created a PR that fixed this issue for me: #959

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

No branches or pull requests

1 participant