While shepherding UrlResolver PR https://github.com/CodexCoder21Organization/UrlResolver/pull/770

Reported (UTC): 2026-07-14 07:56

While shepherding UrlResolver PR https://github.com/CodexCoder21Organization/UrlResolver/pull/770 at head 2acea3500047c26fafd97fccfc100b7d761e9330, remote buildtest runs 7a47af0c and 69ecf485 both failed testRelayRestartSameIdentityReattach with the identical assertion after the existing 30-second recovery budget: the fresh client could not resolve the provider after relay re-attachment, with both HTTP relay forwarding and direct libp2p connection failing against the test's reserved 203.0.113.42 direct address. The identical head passed this test in GitHub Actions and in remote run 9173ad87, and PR 770's changes concern gossip retained-heap admission/test guards rather than relay restart behavior. Impact: otherwise high-pass-count remote suites cannot turn green; repeated full 1102-test reruns are expensive and themselves exposed to unrelated infrastructure failures. No timeout was increased and no test was changed. Suggested durable fix: create a reliable contention reproducer for relay reattachment, capture relay/server/client diagnostics on assertion failure, and fix the actual lost reattachment/forwarding mechanism or runner isolation issue rather than raising the 30-second budget.

Production verification — 2026-07-17

Status: STILL EXISTS. Live GitHub verification found 1 referenced tracker(s) still open: https://github.com/CodexCoder21Organization/UrlResolver/pull/770. A live ProductionHealth connection also emitted repeated NothingToCompleteException gossip failures, while the stopped HardwareControlFabric daemon log ends with Netty ByteBuf leak reports.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.