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
Log before+after ChannelMonitor/Manager updates for visibility
I realized on my own node that I don't have any visibility into how
long a monitor or manager persistence call takes, potentially
blocking other operations. This makes it much more clear by adding
a relevant log_trace!() print immediately before and immediately
after persistence.
// because the update is bogus, ultimately the error that's returned
138
138
// should be a PermanentFailure.
139
139
ifletErr(ChannelMonitorUpdateErr::PermanentFailure) = chain_mon.chain_monitor.update_channel(outpoint, update.clone()){}else{panic!("Expected monitor error to be permanent");}
140
-
logger.assert_log_contains("lightning::chain::chainmonitor".to_string(),"Failed to persist channel monitor update: TemporaryFailure".to_string(),1);
140
+
logger.assert_log_regex("lightning::chain::chainmonitor".to_string(),regex::Regex::new("Failed to persist ChannelMonitor update for channel [0-9a-f]*: TemporaryFailure").unwrap(),1);
0 commit comments