ServicesServer ignores it:
|
update = history_receiver.recv() => |
|
{ |
|
if let Some(update) = update |
|
{ |
|
if let NetworkStateChange::NewServer(new_server) = &update.change |
|
{ |
|
if new_server.server == self.node.id() |
|
{ |
|
self.burst_to_network().await; |
|
} |
|
} |
|
} |
|
} |
but HistoryServer breaks the loop:
|
update = history_receiver.recv() => |
|
{ |
|
let Some(update) = update else { break; }; |
|
|
|
if let Err(error) = self.handle_history_update(update).await { |
|
tracing::error!(?error, "Error return handling history update"); |
|
} |
|
} |
HistoryServer is probably the correct one here, it looks like ServicesServer would enter an infinite loop when the associated sender is dropped
ServicesServer ignores it:
sable/sable_services/src/server/mod.rs
Lines 109 to 121 in 3c6bc2f
but HistoryServer breaks the loop:
sable/sable_history/src/server/mod.rs
Lines 68 to 75 in 3c6bc2f
HistoryServer is probably the correct one here, it looks like ServicesServer would enter an infinite loop when the associated sender is dropped