fix(iroh): better waiting for the NodeAddr to be ready in the echo example

[flub]

Description

This is a major footgun right now, and even this basic example gets it wrong.

Breaking Changes

Notes & open questions

There might be other examples affected, I didn't look.

My first version was very different, and absolutely horrible to write and still failed because of obscure borrowing errors. This is probably rather difficult for people new to rust. Maybe we need to provide a better helper function?

Change checklist

• Self-review.

[github-actions]

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3424/docs/iroh/

Last updated: 2025-08-01T10:04:55Z

[github-actions]

Netsim report & logs for this PR have been generated and is available at: LOGS
This report will remain available for 3 days.

Last updated for commit: 36b847c

[matheus23]

This complicates the example quite a bit.

If this is how we should wait for connectivity, should we update the way that node_addr() works?

This is a major footgun right now, and even this basic example gets it wrong.

Can you explain what exactly the example gets wrong? What's the failure scenario that you're seeing?

[flub]

This complicates the example quite a bit.

Yes it does!

If this is how we should wait for connectivity, should we update the way that node_addr() works?

Maybe.

This is a major footgun right now, and even this basic example gets it wrong.

Can you explain what exactly the example gets wrong? What's the failure scenario that you're seeing?

Users keep running into the cases where they use .node_addr().initialized() and end up with an address that does not have a relay URL inside it. And then run into connectivity problems.