Update outdated comment due to var renames
What the developer wrote
Authored by Valentine Wallace
Update outdated comment due to var renames
What changed, and why it matters
This is a documentation-only change that updates an internal code comment to match renamed variable names. No code behavior was altered, and there is no security impact.
No action required; this is a non-functional comment update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies a single comment in lightning/src/ln/channelmanager.rs, replacing references to forward_htlcs, pending_intercepted_htlcs, and decode_update_add_htlcs with their _legacy suffixed counterparts. The surrounding executable code is unchanged.
Changed components
lightning/src/ln/channelmanager.rs (comment only)Inspect captured patch +4 / −3
diff --git a/lightning/src/ln/channelmanager.rs b/lightning/src/ln/channelmanager.rs
index 92ab422..bc55c4e 100644
--- a/lightning/src/ln/channelmanager.rs
+++ b/lightning/src/ln/channelmanager.rs
@@ -18074,9 +18074,10 @@ where
}
// The ChannelMonitor is now responsible for this HTLC's
// failure/success and will let us know what its outcome is. If we
- // still have an entry for this HTLC in `forward_htlcs`,
- // `pending_intercepted_htlcs`, or `decode_update_add_htlcs`, we were apparently not
- // persisted after the monitor was when forwarding the payment.
+ // still have an entry for this HTLC in `forward_htlcs_legacy`,
+ // `pending_intercepted_htlcs_legacy`, or
+ // `decode_update_add_htlcs_legacy`, we were apparently not persisted
+ // after the monitor was when forwarding the payment.
dedup_decode_update_add_htlcs(
&mut decode_update_add_htlcs_legacy,
&prev_hop_data,
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.