-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Windows connect ECONNREFUSED #369
Comments
I’m seeing the same problem on Linux. For me it was caused by GoogleChrome/chrome-launcher#251. That bug has been fixed but loki sill uses an old version of |
geigerzaehler
added a commit
to geigerzaehler/loki
that referenced
this issue
Apr 2, 2022
This fixes an issue where chrome would fail to launch if `localhost` resolved to the IPv6 address `::1` on Node 17. Fixes oblador#369. Signed-off-by: Thomas Scholtes <[email protected]>
oblador
pushed a commit
to geigerzaehler/loki
that referenced
this issue
Apr 29, 2022
This fixes an issue where chrome would fail to launch if `localhost` resolved to the IPv6 address `::1` on Node 17. Fixes oblador#369. Signed-off-by: Thomas Scholtes <[email protected]>
oblador
pushed a commit
to geigerzaehler/loki
that referenced
this issue
Apr 29, 2022
This fixes an issue where chrome would fail to launch if `localhost` resolved to the IPv6 address `::1` on Node 17. Fixes oblador#369. Signed-off-by: Thomas Scholtes <[email protected]>
oblador
pushed a commit
that referenced
this issue
Apr 29, 2022
This fixes an issue where chrome would fail to launch if `localhost` resolved to the IPv6 address `::1` on Node 17. Fixes #369. Signed-off-by: Thomas Scholtes <[email protected]>
any fixes for this? still getting the error with windows witn node 18.
any chances to test with chrome-launcher 0.15.1? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to run tests on windows 10
npx loki test
configuration
At the same time, everything works fine in the same repository on the mac os
Is there a solution? did not find similar issues
The text was updated successfully, but these errors were encountered: