Skip to main content

Module output

Module output 

Source
Expand description

Output path.

The worker → SpawnerAdapter → engine output path. All structuring is completed inside the SpawnerAdapter; by the time an event reaches the engine it is a Rust-typed OutputEvent. The wire form the worker uses (stdout / NDJSON / file path / IPC) is opaque to the engine.

The WorkerResult type was folded into OutputEvent::Final.

§Canonical type locations

OutputEvent and ContentRef are canonical in crate::store::output; this module is narrowed to re-exports plus the engine-specific OutputSink / EngineSink.

Re-exports§

pub use crate::store::output::ContentRef;
pub use crate::store::output::OutputEvent;

Structs§

EngineSink
Concrete OutputSink — the default implementation that closes over engine, token, task_id, and attempt, and calls engine.submit_output for every emit. Injected by the InProcSpawner into WorkerInvocation.

Traits§

OutputSink
Sink used inside a worker function to emit events. The InProcSpawner injects one into WorkerInvocation. The ProcessSpawner / child-process pull path folds stdout / IPC into OutputEvent internally and calls engine.submit_output directly, so it does not go through OutputSink (it lands in the same engine state, but not via this trait).