Request: IPv6 support for open-vsx.org

[danopia]

Hi, I have one of the OSS Code distributions running on an IPv6-only server and I found that it was unable to install extensions due to open-vsx.org being unreachable.

I see that open-vsx.org doesn't have an AAAA record. Is it practical to set up an IPv6 address / an AAAA record? Or will it stay this way?

Log samples

With internal-only IPv4, Code times out:

[2022-11-27 21:59:51.201] [window] [error] ["Error: connect ETIMEDOUT 198.41.30.195:443","    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)"]
[2022-11-27 21:59:51.221] [window] [error] connect ETIMEDOUT 198.41.30.195:443: Error: connect ETIMEDOUT 198.41.30.195:443
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)

Without a default IPv4 route, Code fails fast:

[2022-11-27 22:10:25.951] [window] [error] ["Error: connect ENETUNREACH 198.41.30.195:443 - Local (0.0.0.0:0)","    at internalConnect (node:net:953:16)","    at defaultTriggerAsyncIdScope (node:internal/async_hooks:465:18)","    at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1097:9)","    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)"]
[2022-11-27 22:10:26.001] [window] [error] connect ENETUNREACH 198.41.30.195:443 - Local (0.0.0.0:0): Error: connect ENETUNREACH 198.41.30.195:443 - Local (0.0.0.0:0)
    at internalConnect (node:net:953:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:465:18)
    at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1097:9)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)

In searching, I found a StackOverflow post which may be the same issue, though I'm not sure: https://stackoverflow.com/questions/74260300/error-fetching-extensions-getaddrinfo-enotfound-open-vsx-org

[kineticsquid]

@danopia Unfortunately we'd have more work to do than some DNS voodoo. Not currently in plan.

[danopia]

Thanks for the info. I see that the server is in Rogers Communications address space so it does sound on-prem and such :)

If there's a low chance of this happening in the foreseeable future feel free to close the issue.
I wanted to file just to have some touch-point on the state of IPv6.

[wget]

This is bugging me as well. I think this question could concern a larger work plan at Eclipse.org. Because from what I see Rogers CA has an AS announcing IPv6 addresses: https://bgp.he.net/AS54412

We are in 2023, you should at least provide a dualstack IPv4/IPv6 network.

Free to discuss this.

[agafgfafa]

I think this question could concern a larger work plan at Eclipse.org

You are correct. We started planning IPv6 in 2006, but here we are in 2024 still without it.