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
Rename Channel's latest-monitor-update fetch method for clarity
`Channel::get_latest_complete_monitor_update_id` no longer refers
to complete updates, but rather ones which were passed to the
`ChannelManager` and which the `CHannel` no longer knows about.
Thus, we rename it `get_latest_unblocked_monitor_update_id`.
if chan.get_latest_complete_monitor_update_id() > max_in_flight_update_id {
8344
+
if chan.get_latest_unblocked_monitor_update_id() > max_in_flight_update_id {
8345
8345
// If the channel is ahead of the monitor, return InvalidValue:
8346
8346
log_error!(args.logger,"A ChannelMonitor is stale compared to the current ChannelManager! This indicates a potentially-critical violation of the chain::Watch API!");
8347
8347
log_error!(args.logger," The ChannelMonitor for channel {} is at update_id {} with update_id through {} in-flight",
0 commit comments