feat(p2p): log the resolved iroh relay set at endpoint spawn#1082
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
📝 WalkthroughWalkthroughIn ChangesRelay Logging
Estimated code review effort: 1 (Trivial) | ~2 minutes Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Also pushed |
During the defra-agent#588 incident the host was flooded by relay open_path retries against n0 canary relays — and nothing in the logs showed which relay infrastructure the endpoint was pointed at. Log the resolved relay URL set once at spawn so canary/staging vs production is visible in every deployment. (The iroh 1.0.1 bump originally on this branch landed via #1084.) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
407985f to
df9299c
Compare
Why
Follow-up to the defra-agent#588 incident (relay
open_pathflood against unreachable n0 canary relays). During the incident nothing in the logs showed which relay infrastructure the endpoint was pointed at — canary vs production was invisible at default verbosity.What
Slimmed down after #1084 merged (which landed the iroh 1.0.1 / gossip 0.101 / blobs 0.103 / tickets 1.0.0 bump this PR originally carried — thanks!). What remains is the observability piece: log the resolved relay URL set once at
spawn_endpointincrates/p2p/src/iroh/endpoint.rs, so every deployment shows its relay infrastructure at startup.Verification
cargo check -p p2p --all-featuresgreen on top of chore(deps): update Iroh to final 1.0 release #1084cargo fmt --checkgreenThe
fix/iroh-1.0-on-v0.15.1branch mentioned earlier is now obsolete (defra-agent pins the #1084 merge rev directly) — I'll delete it.🤖 Generated with Claude Code