Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

feat: stop continuous MTR probing of hops with unknown IP (*)

probe() previously sent a probe every tick (default 1s) to every hop
from TTL 1 to hopCount regardless of whether that hop had ever
responded during discovery. A hop behind a router that silently drops
or filters ICMP TTL-exceeded would render as "*" forever but still
accumulate Sent/loss stats from probes aimed at an address we never
actually learned.

probe() now skips any hop whose MTRStats.HasIP is false. The hop's row
still renders in the MTR table (discover() already created the slot
via EnsureLen), just frozen at whatever Sent/Recv it had going in —
typically 0/0, so it reads as "*" with no loss data rather than
climbing toward 100% loss on an address that was never dialled.

discover() and the periodic rediscovery pass (every 10 min by default)
are untouched: they still probe every TTL up to MaxHops, so a hop that
starts responding later is picked up on the next rediscovery.