Andrew Mackenzie

BTW: "deadline" is currently 1s, not sure what a good value would be. I have extended to make sure, and then the issue I get is that the same device...

Thanks for the response! All the code is open source, that test support method can be seen in full here: https://github.com/andrewdavidmackenzie/pigg/blob/master/hw_test/tests/mdns_support.rs#L25 I'm making some changes in a branch to debug,...

only fails sometimes, not always... repeated until it fails, and this is the output: ``` ---- mdns_discover_and_connect_tcp stdout ---- Addresses: {192.168.1.101} Hostname: host1.local. Fullname: e66138528350be2b._pigg._tcp.local. Discovered device: e66138528350be2b : ip...

some other times I still get: ``` ---- mdns_discover_and_connect_tcp stdout ---- Addresses: {} Hostname: host1.local. Fullname: 00000000e91e810c._pigg._tcp.local. thread 'mdns_discover_and_connect_tcp' panicked at hw_test/tests/mdns_support.rs:36:22: Failed to get IP ```

After fixing the hostname, I cannot reproduce either failure.... I trust that fixes it. Thanks for your help and patience!

I spoke too soon. Here is a case where Addresses is empty again: ``` ---- mdns_discover_and_connect_tcp stdout ---- Addresses: {} Hostname: 00000000e91e810c.local. Fullname: 00000000e91e810c._pigg._tcp.local. ```

Didn't mean to close, finger trouble :-( On my embedded (Pi Pico) devices I create a unique hostname to use for mDNS. In Pi Zero instance, I do the same...

``` ---- connect_and_disconnect_iroh stdout ---- Addresses: {192.168.1.101} Hostname: e66138528350be2b.local. Fullname: e66138528350be2b._pigg._tcp.local. Addresses: {192.168.1.116} Hostname: host1.local. Fullname: f796c3e764ad1c09._pigg._tcp.local. Addresses: {fe80::f4fe:d0c0:2415:6a05} Hostname: 00000000e91e810c.local. Fullname: 00000000e91e810c._pigg._tcp.local. ``` To my surprise, a v6 IP...

Thanks @nate-trojian I raised the issue recently in Iced discord. Someone chipped in saying it was planned for the next release (0.14.0), but when I looked at the milestone for...

@nate-trojian presumably that change is needed there to be at the right moment in iced startup/initialization? Did your app just have the usual calls to iced on start-up to have...