You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user has issues with a payment, the most obvious thing they'll
do is check logs for the payment hash. Thus, we should ensure our
logs that show a payment's lifecycle include the payment hash and
are emitted (a) as soon as LDK learns of the payment, (b) once the
payment goes out to the peer (which is already reasonably covered
in the commitment transaction building logs) and (c) when the
payment ultimately is fulfilled or fails.
Here we improve our logs for both (a) and (c).
let need_holding_cell = (self.context.channel_state & (ChannelState::AwaitingRemoteRevoke as u32 | ChannelState::MonitorUpdateInProgress as u32)) != 0;
5191
-
log_debug!(logger, "Pushing new outbound HTLC for {} msat {}", amount_msat,
5193
+
log_debug!(logger, "Pushing new outbound HTLC with hash {} for {} msat {}",
5194
+
payment_hash, amount_msat,
5192
5195
if force_holding_cell { "into holding cell" }
5193
5196
else if need_holding_cell { "into holding cell as we're awaiting an RAA or monitor" }
0 commit comments