Skip to main content

Module runner

Module runner 

Source
Available on crate feature serve only.
Expand description

The run lifecycle: validate + queue a submission (submit), then run it under a permit. A cancel / timeout / shutdown trigger cooperatively cancels the pipeline (so a buffered sink flushes at its next page boundary, #146 H16) and grants a bounded flush grace before hard-dropping it; the task then finalizes an authoritative terminal status. See spec §7 + §20.

Structs§

SubmitRequest
POST /v1/runs request body.
SubmitResponse
POST /v1/runs success body (202).

Enums§

ConfigFormatWire
Wire enum mirroring load::ConfigFormat with serde rename.

Functions§

resume_claimed_run
Re-run a claimed Pending run on this instance (cluster mode). Reconstructs the execution inputs from the persisted record (re-resolving config with this instance’s own env/credentials), acquires a permit, and runs the shared tail.
resume_claimed_shard
Execute one claimed shard (Mode B): rebuild + narrow the source to the shard, run it under a permit, owner-fenced-finalize the shard, then finalize the parent run once every shard is terminal.
submit
Validate, idempotency-claim, queue, and spawn a submission.