Connection to gadgets on IPv6-enabled host is failing#876
Connection to gadgets on IPv6-enabled host is failing#876lelutin wants to merge 1 commit intopuremourning:masterfrom
Conversation
On hosts where IPv6 is enabled and preferred by the system, gadgets might be listening to ::1 instead of 127.0.0.1. In those situations, vimspector times out, unable to connect to the gadget even though they've both agreed about which port to use. Changing the default host value to 'localhost' makes it possible for IPv6-enabled hosts to use the same default in vimspector than in the gadgets.
|
This change is |
|
Thanks for the PR, but unfortunately, we force the use of IPv4 for the exact opposite reason! See 4206d0e for example. There were a swathe of issues when using I think if your server uses IPv6 by default, you just need to set host to |
|
Oh I see, thanks for the details. It's a bit unfortunate to still be defaulting to ipv4 nowadays but I can understand that ipv6 has still not established its hegemony and so ipv4 keeps on being the safe default. So instead of this MR, maybe we could add a quick mention of the default value (and thus address family) for |
|
As mentioned, this would regress existing fixes. IPv4 ain't going nowhere so I don't see any reason to change this. The workaround is trivial for the very few people who only listen on IPv6 addresses. |
2 participants
On hosts where IPv6 is enabled and preferred by the system, gadgets might be listening to ::1 instead of 127.0.0.1. In those situations, vimspector times out, unable to connect to the gadget even though they've both agreed about which port to use.
Changing the default host value to 'localhost' makes it possible for IPv6-enabled hosts to use the same default in vimspector than in the gadgets.