Struct PreparedTune 

pub struct PreparedTune { /* private fields */ }

Everything prepare resolves before a tune’s long-running polling phase can start: the already-validated/defaulted TuneArgs, the resolved template and derived tags, a connected driver, the built LoopConfig, the run’s start time, and the response level (if any) to write back at the end – plus the tune_runs row’s assigned id.

Exists to split [run_with_ctrl_c]’s single monolithic body into a fast, synchronous-ish setup phase (this struct’s construction: template lookup, tag derivation, driver connect, and the tune_runs insert that assigns PreparedTune::run_id) and a long-running phase (drive/[execute]’s actual polling loop, potentially minutes long) – so an HTTP caller (bhtune-server’s POST /api/runs) can run the first phase inline in its request handler (fast enough to await directly, and any failure here – bad template name, unreachable driver – is exactly the kind of problem an HTTP client expects a synchronous error response for) and tokio::spawn the second, returning the assigned run_id immediately rather than blocking the HTTP response for the whole test.

Every field but run_id is private: a caller that isn’t this module has no legitimate reason to inspect a template/tags/driver/config mid-flight, only to hand the whole prepared bundle to drive (or, internally, [run_with_ctrl_c]) unchanged.

Implementations

impl PreparedTune

pub fn run_id(&self) -> i64

The tune_runs row id assigned to this run – returned to an HTTP caller immediately (before the run has necessarily finished, or even started polling) so it can be used to poll GET /api/runs/{id} or issue POST /api/runs/{id}/cancel.