Struct BuildDeathBreaker 

pub struct BuildDeathBreaker { /* private fields */ }

SQLite-backed, root/domain/fingerprint-isolated death history.

Implementations

impl BuildDeathBreaker

pub fn open(path: impl Into<PathBuf>) -> Result<Self>

pub fn path(&self) -> &Path

pub fn admit( &self, key: &BreakerKey, committed_extracted_bytes: u64, ) -> Result<BreakerAdmission>

pub fn admit_at( &self, key: &BreakerKey, committed_extracted_bytes: u64, now_ms: u64, ) -> Result<BreakerAdmission>

pub fn record_attributed_death( &self, key: &BreakerKey, attempt_id: &str, committed_extracted_bytes_at_death: u64, durable_burn_ms: u64, ) -> Result<Option<BuildSuspension>>

Charge one already attributed exact-process death. Callers must only use this after validating a durable expensive-phase marker and reading the staging metadata counter. Repeating the same attempt is idempotent.

pub fn record_attributed_death_at( &self, key: &BreakerKey, attempt_id: &str, committed_extracted_bytes_at_death: u64, durable_burn_ms: u64, now_ms: u64, ) -> Result<Option<BuildSuspension>>

pub fn record_durable_burn_at( &self, key: &BreakerKey, durable_burn_ms: u64, now_ms: u64, ) -> Result<Option<BuildSuspension>>

Credit cannot reset the burn ceiling. This is used for live heartbeat checkpoints whose elapsed interval has already been durably bounded.

pub fn record_ready_publication(&self, key: &BreakerKey) -> Result<()>

A ready pointer flip is the only automatic full reset. Staged commits do not call this method and therefore cannot launder a death loop.

pub fn explicit_reset(&self, key: &BreakerKey) -> Result<()>

Doctor and force-rebuild use this explicit, tuple-scoped full reset.

pub fn suspension(&self, key: &BreakerKey) -> Result<Option<BuildSuspension>>

pub fn suspension_at( &self, key: &BreakerKey, now_ms: u64, ) -> Result<Option<BuildSuspension>>

pub fn active_suspensions_for_root( &self, root_id: &str, ) -> Result<Vec<BuildSuspension>>

pub fn active_suspensions_for_root_at( &self, root_id: &str, now_ms: u64, ) -> Result<Vec<BuildSuspension>>

Read every still-active domain suspension for one root from the durable breaker rows. Health and doctor snapshots use this instead of inferring a suspension from transient worker state, so every surface reports the same persisted reason and counters.