From 726461c1930197566aa322631ad2bdb5c646a297 Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Thu, 28 May 2026 21:13:26 +0000 Subject: [PATCH] node/tests: reword handshake regression-test doc-comments Drop an internal tracker reference from the doc-comments of the should_admit_msg1 and udp.outbound_only rekey regression tests; the prose now describes the scenario directly. --- src/node/tests/handshake.rs | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/node/tests/handshake.rs b/src/node/tests/handshake.rs index 281732e..1c6507f 100644 --- a/src/node/tests/handshake.rs +++ b/src/node/tests/handshake.rs @@ -1152,7 +1152,7 @@ async fn test_should_admit_msg1_rejects_fresh_when_accept_off() { assert!(!node.should_admit_msg1(transport_id, &addr)); } -/// ISSUE-2026-0004 regression test: `should_admit_msg1` admits rekey/restart +/// Regression test: `should_admit_msg1` admits rekey/restart /// msg1 from a peer with an existing link even when the transport has /// accept_connections=false. Without this, the dual-init tie-breaker /// deadlocks (the larger-NodeAddr side drops the winner's rekey msg1). @@ -1224,7 +1224,8 @@ async fn test_should_admit_msg1_admits_rekey_when_udp_accept_off() { } /// Regression test for the udp.outbound_only rekey loop observed in -/// production 2026-04-30 (parallel to ISSUE-2026-0004). +/// production 2026-04-30 (parallel to the rekey/restart admission case +/// above). /// /// Production scenario: nomad runs `udp.outbound_only=true` with peer /// core-vm configured by hostname (`core-vm.tail65015.ts.net:2121`).