What the developer wrote
Authored by Elle Mouton
graph: fix log formatting
What changed, and why it matters
This is a one-character logging fix. The developer changed a debug log message from using %x (which prints data as hexadecimal) to %s (which prints as a regular string). It does not change program behavior, fix a crash, or address any security issue. It is purely a cosmetic/log readability correction.
No security action needed. Treat as a routine code-quality/logging fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In graph/builder.go, the IsStaleNode method’s debug log changed the format verb for a route.Vertex node from %x to %s. route.Vertex is a fixed-length byte array type that likely implements Stringer/encoding.TextMarshaler, so %s is the correct verb. The previous %x would have produced a hex-encoded representation rather than the expected human-readable node ID. This is a non-functional logging-only change.
Changed components
graph/builder.goIsStaleNode debug log formattingInspect captured patch +1 / −1
diff --git a/graph/builder.go b/graph/builder.go
index b446d1a..59e9b19 100644
--- a/graph/builder.go
+++ b/graph/builder.go
@@ -1313,7 +1313,7 @@ func (b *Builder) IsStaleNode(ctx context.Context, node route.Vertex,
// then we know that this is actually a stale announcement.
err := b.assertNodeAnnFreshness(ctx, node, timestamp)
if err != nil {
- log.Debugf("Checking stale node %x got %v", node, err)
+ log.Debugf("Checking stale node %s got %v", node, err)
return true
}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.