J. Nick Koston

Results 1005 comments of J. Nick Koston

Looks like macos has MULTICAST on lo0 ``` lo0: flags=8049 mtu 16384 options=1203 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 nd6 options=201 ```

linux 4.4.x ``` lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:24830216 errors:0 dropped:0 overruns:0 frame:0 TX packets:24830216 errors:0 dropped:0 overruns:0...

``` 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host...

In HA we already explicitly exclude loopback ``` zc_args["interfaces"] = [ str(source_ip) for source_ip in await network.async_get_enabled_source_ips(hass) if not source_ip.is_loopback and not (isinstance(source_ip, IPv6Address) and source_ip.is_global) and not ( isinstance(source_ip,...

There is even a docstring that loopback doesn't work. Someone might need it though so I think we can change `InterfaceChoice.All` to exclude loopback, and add `InterfaceChoice.AllWithLoopback`

That would be better but realistically we don't have that information unless your PR gets merged

Seems to only affect the systems we have[ binary wheels for ie i686/x86_64 ](https://wheels.home-assistant.io/musllinux/) previous report https://github.com/langchain-ai/langchain/issues/8361

[pydantic-1.10.12](https://wheels.home-assistant.io/musllinux/pydantic-1.10.12-cp311-cp311-musllinux_1_2_i686.whl) doesn't seem to have the problem, but I think they were built with cython 0.29.x Maybe cython 3.x issue?

I think that won't get used until its in `build-system` https://peps.python.org/pep-0518/#build-system-table

If I create a `pyproject.toml` ``` pydantic % cat pyproject.toml [build-system] requires = ["setuptools", "wheel", "Cython==0.29.32;sys_platform!='win32'"] ``` It uses cython 0.29.32