Struct Finalize 

pub struct Finalize {
    pub backend_address: String,
}

Specifies the binding and operation parameters for a thread that saves finalized tasks to the DB

Fields

backend_address: String

the DB address to bind on

Implementations

impl Finalize

pub fn start(&self, done_rx: Receiver<TaskReport>) -> Result<(), Box<dyn Error>>

Start the finalize loop: block on the bounded done channel for the first report of a batch, then accumulate more via [accumulate_batch] until the size (N, finalize_batch_size) or time (T, finalize_flush_ms) threshold trips, and persist the whole batch in one mark_done transaction. This is event-driven (woken the instant a result lands), backpressured by the bounded channel (not the old Mutex<Vec> + panic-backstop), and coalesced so DB write frequency stays bounded under load (phase 2). The outer recv_timeout(1s) preserves the 1s idle cadence for the refresh-on-drain. Shutdown is driven entirely by Disconnected (every producer’s done-sender dropped): in a bounded run the manager drops the last sender once the ventilator + sink have finished, and the finalize thread then drains the remaining reports and stops (KNOWN_ISSUES D-5 — no per-thread job_limit counter, which was the unit that disagreed with the other two threads).