peer: include ping pong-size in debug summaries

Expose num_pong_bytes in the ping message summary so ignored no-reply
pings are visible in debug logs. Add a focused test covering the summary
output for the sentinel range.

Author: yyforyongyu

peer/brontide.go

@@ -2598,7 +2598,8 @@ func messageSummary(msg lnwire.Message) string {
 			msg.NodeID, time.Unix(int64(msg.Timestamp), 0))
 
 	case *lnwire.Ping:
-		return fmt.Sprintf("ping_bytes=%x", msg.PaddingBytes[:])
+		return fmt.Sprintf("num_pong_bytes=%d, len(ping_bytes)=%d",
+			msg.NumPongBytes, len(msg.PaddingBytes[:]))
 
 	case *lnwire.Pong:
 		return fmt.Sprintf("len(pong_bytes)=%d", len(msg.PongBytes[:]))

peer/brontide_test.go

@@ -1143,6 +1143,26 @@ func TestPeerIgnoresPingWithoutPongReply(t *testing.T) {
 	require.Len(t, pong.PongBytes, 1)
 }
 
+// TestMessageSummaryPingIncludesNumPongBytes ensures the debug summary for a
+// ping exposes the requested pong size, which makes ignored no-reply pings
+// visible without requiring trace-level logging.
+func TestMessageSummaryPingIncludesNumPongBytes(t *testing.T) {
+	t.Parallel()
+
+	// Arrange: Build a ping that uses the BOLT 1 no-reply sentinel range.
+	msg := &lnwire.Ping{
+		NumPongBytes: 65535,
+		PaddingBytes: []byte{1, 2, 3},
+	}
+
+	// Act: Generate the human-readable message summary.
+	summary := messageSummary(msg)
+
+	// Assert: The summary includes both the requested pong size and payload
+	// length so debug logs can explain why no pong was sent.
+	require.Equal(t, "num_pong_bytes=65535, len(ping_bytes)=3", summary)
+}
+
 // TestUpdateNextRevocation checks that the method `updateNextRevocation` is
 // behave as expected.
 func TestUpdateNextRevocation(t *testing.T) {