Enum Pass 

pub enum Pass {
    Detailed(PassRecord),
    Summary {
        at: DateTime<Utc>,
        bytes_freed: u64,
        dirs_removed: usize,
        repos_touched: usize,
        dirs: Option<Vec<PrunedDir>>,
    },
}

One pass as devp history sees it, from whichever source knows about it.

The two variants are not a design choice so much as an admission: this log starts at constants::PRUNE_LOG_STARTS_AT, and every pass a machine ran before that upgrade exists only as the registry’s four numbers. Showing those as a gap would read as data loss, and leaving them out entirely would make devp history disagree with the pass count devp stats prints two lines above it.

Variants

Detailed(PassRecord)

A pass this log recorded in full.

Summary

A pass known only from the registry’s summary.

Fields

at: DateTime<Utc>

bytes_freed: u64

dirs_removed: usize

repos_touched: usize

dirs: Option<Vec<PrunedDir>>

The directory list, when this happens to be the pass last_prune describes.

Implementations

impl Pass

pub fn at(&self) -> DateTime<Utc>

pub fn bytes_freed(&self) -> u64

pub fn dirs_removed(&self) -> usize

pub fn repos_touched(&self) -> usize

pub fn trigger(&self) -> Option<Trigger>

What started the pass, where that is known.

None for a pass recovered from the registry summary: the summary has never carried a trigger, so a machine that pruned before 1.17.0 cannot say afterwards which of those passes it typed and which the scheduler ran.

pub fn dirs(&self) -> Option<&[PrunedDir]>

The directory list, where one is known.

Trait Implementations

impl Clone for Pass

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Pass

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.