What the developer wrote
Authored by ziggie
routing: fix log output line
What changed, and why it matters
This is a trivial log message formatting fix. The original debug log line had a formatting placeholder but no value supplied, which would have printed an ugly '%!d(MISSING)' in logs. The patch adds the missing count so the log line displays correctly. It has no security relevance.
No security action needed. Treat as normal code-quality/maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In routing/control_tower.go, the debug log call log.Debugf(“Scanning for inflight payments finished”, len(inflightPayments)) used fmt-style formatting but did not include a %d verb, so Go’s fmt package would emit a ‘%!d(MISSING)’ artifact. The commit changes the format string to include ‘found_inflight=%d’ and passes len(inflightPayments). This is purely a logging correctness/cosmetic change; no control flow, state, or cryptographic behavior is altered.
Changed components
routing/control_tower.go:SubscribeAllPayments debug loggingInspect captured patch +2 / −2
diff --git a/routing/control_tower.go b/routing/control_tower.go
index 1c246f1..791faa5 100644
--- a/routing/control_tower.go
+++ b/routing/control_tower.go
@@ -366,8 +366,8 @@ func (p *controlTower) SubscribeAllPayments() (ControlTowerSubscriber, error) {
if err != nil {
return nil, err
}
- log.Debugf("Scanning for inflight payments finished",
- len(inflightPayments))
+ log.Debugf("Scanning for inflight payments finished: "+
+ "found_inflight=%d", len(inflightPayments))
for index := range inflightPayments {
// Always write current payment state to the channel.
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.