From 40d1a5bca76a9855792bd32c19fac55155f40479 Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Mon, 13 Jul 2026 23:24:56 +0000 Subject: [PATCH] node: pin the max-peers inbound-reject log to the handshake tracing target The debug log for rejecting an over-cap inbound connection is emitted from the peer-action executor, under that module's tracing target. Nodes that raise only the handshake module to debug (leaving other modules at info) no longer surfaced the rejection, so cap-enforcement events were invisible in their logs. Re-pin the log to the handshake target, matching the adjacent promoting-inbound log, so the rejection stays visible under a handshake=debug filter regardless of the executor module's own level. --- src/node/dataplane/peer_actions.rs | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/node/dataplane/peer_actions.rs b/src/node/dataplane/peer_actions.rs index 2d85e9d..95f4651 100644 --- a/src/node/dataplane/peer_actions.rs +++ b/src/node/dataplane/peer_actions.rs @@ -276,6 +276,12 @@ impl Node { // failures remain at warn. if matches!(e, NodeError::MaxPeersExceeded { .. }) { debug!( + // Emit under the handshake target (same as the + // "promoting inbound" line above) so this stays + // visible wherever inbound handshake events are + // logged at debug, independent of this module's + // own log level. + target: "fips::node::handlers::handshake", peer = %self.peer_display_name(ambient.verified_identity.node_addr()), max = self.max_peers(), "Rejecting inbound connection at max_peers cap (no promotion)"