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

Spandx does not work on WSL2 #352

Closed
kelsS opened this issue Jan 7, 2025 · 3 comments
Closed

Spandx does not work on WSL2 #352

kelsS opened this issue Jan 7, 2025 · 3 comments

Comments

@kelsS
Copy link

kelsS commented Jan 7, 2025

When working in any project using spandx with open: true browser tab never opens and the opn package throws the following error:

(node:22616) UnhandledPromiseRejectionWarning: Error: Exited with code 3
    at ChildProcess.<anonymous> (/home/kelss/github/rh/community/node_modules/opn/index.js:85:13)
    at Object.onceWrapper (events.js:520:26)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1088:16)
    at Socket.<anonymous> (internal/child_process.js:446:11)
    at Socket.emit (events.js:400:28)
    at Pipe.<anonymous> (net.js:686:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:22616) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:22616) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

There is also an error when loading the proxy urls:

net::ERR_CERT_AUTHORITY_INVALID

Even though I have ran npm run mkcert and spandx says my ssl certs are valid.

This is a major blocking issue, I cannot access any local development environments through my WSL2 machine,

@kelsS
Copy link
Author

kelsS commented Jan 7, 2025

@mwcz do you happen to know a fix for this? I feel like we discussed the issue before but I cannot remember if or how we fixed it.

@kelsS kelsS closed this as completed Jan 7, 2025
@kelsS
Copy link
Author

kelsS commented Jan 7, 2025

Apologies this is a duplicate ticket

#280

@mwcz
Copy link
Contributor

mwcz commented Jan 16, 2025

Fixed by updating the Windows hosts file with the .foo entries.

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

2 participants