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

Percy exec fails binding to ipv6 #1491

Closed
danpowell88 opened this issue Jan 9, 2024 · 2 comments
Closed

Percy exec fails binding to ipv6 #1491

danpowell88 opened this issue Jan 9, 2024 · 2 comments
Labels
🍞 stale Closed due to inactivity

Comments

@danpowell88
Copy link

The problem

Cannot run percy exec

npx @percy/cli exec:start -v

Environment

  • Node version: 14.19.1
  • @percy/cli version: 1.27.7
  • OS version:
  • Type of shell command-line [interface]: bash

Details

Running exec on 1.27.7. tries to bind to an ipv6 interface which is not available on this machine and thus fails, revering back to 1.24.4 resolves the issue. I suspect this was introduced with #1463

Debug logs

[a@b~]$ npx @percy/cli exec:start -v
[percy:config] Config file not found (0ms)
[percy:client] Creating a new build... (34ms)
[percy:env] Detected ci as null (0ms)
[percy:env] Detected commit as null (0ms)
[percy:env] Detected branch as null (0ms)
[percy:env] Detected git as {"sha":null,"branch":null,"message":null,"authorName":null,"authorEmail":null,"committedAt":null,"committerName":null,"committerEmail":null} (17ms)
[percy:env] Detected target as {"commit":null,"branch":null} (0ms)
[percy:env] Detected pullRequest as null (1ms)
[percy:env] Detected parallel as {"total":null,"nonce":null} (0ms)
[percy:env] Detected partial as false (0ms)
[percy:env] Detected info as null (0ms)
[percy:core:browser] Launching browser (430ms)
[percy:core:browser] Browser connected [12436]: HeadlessChrome/120.0.6099.109 (109ms)
[percy:core:queue] Clearing discovery queue, queued state: 0, pending state: 0 (5ms)
[percy:core:browser] Closing browser (1ms)
[percy:core:browser] Browser closed (18ms)
[percy:core:queue] Clearing snapshot queue, queued state: 0, pending state: 0 (0ms)
[percy:cli] Error: listen EAFNOSUPPORT: address family not supported :::5338
    at Server.setupListenHandle [as _listen2] (net.js:1314:21)
    at listenInCluster (net.js:1379:12)
    at doListen (net.js:1516:7)
    at processTicksAndRejections (internal/process/task_queues.js:83:21) (0ms)

ifconfig output

[a@b ~]$ ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:xx:xx:xx:xx  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.x.x.x netmask 255.255.255.224  broadcast 172.x.x.x
        ether 00:50:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 4415796  bytes 3831634706 (3.5 GiB)
        RX errors 0  dropped 174  overruns 0  frame 0
        TX packets 2707257  bytes 2881026982 (2.6 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 310055  bytes 2492805382 (2.3 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 310055  bytes 2492805382 (2.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Workaround

Setting PERCY_SERVER_HOST=localhost will resolve the issue

Copy link

This issue is stale because it has been open for more than 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the 🍞 stale Closed due to inactivity label Jan 23, 2024
Copy link

github-actions bot commented Feb 6, 2024

This issue was closed because it has been stalled for 28 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍞 stale Closed due to inactivity
Projects
None yet
Development

No branches or pull requests

1 participant