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
Handle events immediately if we are running during block connection
During block connection, we cannot apply `ChannelMonitorUpdate`s if
we're running during the startup sequence (i.e. before the user has
called any methods outside of block connection). We previously
handled this by simply always pushing any `ChannelMonitorUpdate`s
generated during block connection into the
`pending_background_events` queue.
However, this results in `ChannelMonitorUpdate`s going through the
queue when we could just push them immediately. Here we explicitly
check `background_events_processed_since_startup` and use that to
decide whether to push updates through the background queue
instead.
nodes[0].node.test_process_background_events();// Required to free the pending background monitor update
353
-
check_added_monitors!(nodes[0],1);
370
+
354
371
let expected_err = "Funding transaction was un-confirmed. Locked at 6 confs, now have 0 confs.";
355
372
if reorg_after_reload || !reload_node {
356
373
handle_announce_close_broadcast_events(&nodes,0,1,true,"Channel closed because of an exception: Funding transaction was un-confirmed. Locked at 6 confs, now have 0 confs.");
0 commit comments