Skip to main content

DEFAULT_MAIN_TIMEOUT_SECS

Constant DEFAULT_MAIN_TIMEOUT_SECS 

Source
pub const DEFAULT_MAIN_TIMEOUT_SECS: f64 = 30.0;
Expand description

How long ONE dispatch may wait for the main thread before the step is failed.

This is not the step’s implicit-wait budget (DEFAULT_TIMEOUT_SECS, §14.3). That one governs re-asking a question whose answer may change — “is it visible yet?”. This one governs a main thread that has not answered at all: a CI runner compositing its first frame on a shared vCPU, a debug build faulting in pages, a compositor stall. Those are properties of the machine, not of the script, which is why DAY_SCRIPT_MAIN_TIMEOUT_SECS can raise it without editing a walkthrough. It was a flat 10s, and a single Windows runner hiccup mid-walkthrough was enough to fail an otherwise perfect 407-step run.

Day API ↩ Guides· daybrite.dev