@@ -3943,8 +3943,8 @@ where
3943
3943
&& matches!(&monitor_update.updates[0], ChannelMonitorUpdateStep::ChannelForceClosed { .. });
3944
3944
// If the ChannelMonitorUpdate is closing a channel that never got past initial
3945
3945
// funding (to have any commitment updates), we'll skip inserting in
3946
- // `update_maps_on_chan_removal `, allowing us to avoid keeping around the PeerState
3947
- // for that peer. In that specific case we expect no entry in the map here. In any
3946
+ // `locked_close_channel `, allowing us to avoid keeping around the PeerState for
3947
+ // that peer. In that specific case we expect no entry in the map here. In any
3948
3948
// other cases, this is a bug, but in production we go ahead and recover by
3949
3949
// inserting the update_id and hoping its right.
3950
3950
debug_assert!(is_closing_unupdated_monitor, "Expected closing monitor against an unused channel, got {:?}", monitor_update);
@@ -8158,9 +8158,8 @@ where
8158
8158
// Note that at this point we've filled in the funding outpoint on our
8159
8159
// channel, but its actually in conflict with another channel. Thus, if
8160
8160
// we call `convert_chan_phase_err` immediately (thus calling
8161
- // `update_maps_on_chan_removal`), we'll remove the existing channel
8162
- // from `outpoint_to_peer`. Thus, we must first unset the funding outpoint
8163
- // on the channel.
8161
+ // `locked_close_channel`), we'll remove the existing channel from `outpoint_to_peer`.
8162
+ // Thus, we must first unset the funding outpoint on the channel.
8164
8163
let err = ChannelError::close($err.to_owned());
8165
8164
chan.unset_funding_info(msg.temporary_channel_id);
8166
8165
return Err(convert_chan_phase_err!(self, peer_state, err, chan, &funded_channel_id, UNFUNDED_CHANNEL).1);
0 commit comments