long startup due to long timeouts on ipv6 for name resolution

[lbe]

What version of Kimi Code CLI is running?

kimi, version 1.12.0

Which open platform/subscription were you using?

Debian 12.13

Which model were you using?

kimi-code

What platform is your computer?

Linux 6.8.12-16-pve x86_64 unknown

What issue are you seeing?

Long startup time!

What steps can reproduce the bug?

It started out of the blue. I exited one kimi session and tried to open a new one so that I would have clean context.

After a lot of back and forth on a chat with Kimi (see Click the link to view conversation with Kimi AI Assistant https://www.kimi.com/share/19c6c845-5712-85a4-8000-000083595df3) it suggested that this could be name resolution issue with ipv6.

When I checked with nslookup, I received 2 ipv4 and 2 ipv6 addresses. I disabled the ipv6 on the computer. kimi now starts quickly as expected.

What is the expected behavior?

kimi should start within a couple of seconds

Additional information

Click the link to view conversation with Kimi AI Assistant https://www.kimi.com/share/19c6c845-5712-85a4-8000-000083595df3

[xiaoju111a]

IPv6 seems to have many problems, so I've simply banned the IPv6 protocol.

[lbe]

That is fine in my case, but having IPV6 supported is a good thing.

Kimi provided:

Python's asyncio and socket.create_connection() have had Happy Eyeballs support since 3.8 (2019). Someone had to actively work to make it this broken — either:

Hopefully that will help.