413b0b5b2b
We were batch removing chains when purging, and then updating the status of the collection for each of those. This makes the range status be out of sync with the real status. This represented no harm to the global sync status, but I've changed it to comply with a correct debug assertion that I got triggered while doing some testing. Also added tests and improved code quality as per @paulhauner 's suggestions.
26 lines
989 B
Rust
26 lines
989 B
Rust
use beacon_chain::{BeaconChain, BeaconChainError, BeaconChainTypes};
|
|
|
|
use lighthouse_network::rpc::StatusMessage;
|
|
/// Trait to produce a `StatusMessage` representing the state of the given `beacon_chain`.
|
|
///
|
|
/// NOTE: The purpose of this is simply to obtain a `StatusMessage` from the `BeaconChain` without
|
|
/// polluting/coupling the type with RPC concepts.
|
|
pub trait ToStatusMessage {
|
|
fn status_message(&self) -> Result<StatusMessage, BeaconChainError>;
|
|
}
|
|
|
|
impl<T: BeaconChainTypes> ToStatusMessage for BeaconChain<T> {
|
|
fn status_message(&self) -> Result<StatusMessage, BeaconChainError> {
|
|
let head_info = self.head_info()?;
|
|
let fork_digest = self.enr_fork_id().fork_digest;
|
|
|
|
Ok(StatusMessage {
|
|
fork_digest,
|
|
finalized_root: head_info.finalized_checkpoint.root,
|
|
finalized_epoch: head_info.finalized_checkpoint.epoch,
|
|
head_root: head_info.block_root,
|
|
head_slot: head_info.slot,
|
|
})
|
|
}
|
|
}
|