Diagnostic Server Fails on macOS 14.4 about cargo HOT 5 CLOSED

Have a shot-in-the-dark. @abhillman could you help verify it?
#13907

from cargo.

Could you run ifconfig lo0 or something similar, and check if the loopback device is up and 127.0.0.1 is its address?

from cargo.

Indeed, loopback is up, but is it assigned a LAN IP. I had noticed this as well; it is quite curious.

$ ifconfig lo0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
	inet 192.168.1.88 netmask 0xffffffff
	nd6 options=201<PERFORMNUD,DAD>
$ ifconfig | rg '127' # no result
$ ifconfig | rg 'localhost' # no result

from cargo.

This appears to resolve the issues with cargo run clippy --fix and the above rust code:

$ sudo ifconfig lo0 alias 127.0.0.1

That said, I don't believe that macOS ships with the 127.0.0.1 alias on lo0. I will see what I can do to run a test with a fresh install on a VM and/or CI. If indeed, macOS does not ship with 127.0.0.1 as a loopback alias, it seems to me that some kind of workaround for cargo may be appropriate. lmkwyt.

from cargo.

Ok, a vm running a fresh install of macOS 14.3 indeed has 127.0.0.1 set up as an alias. I will see what happens with an upgrade to 14.4. This may just be a "my box" (perhaps sometimes other boxes?) problem.

from cargo.