Skip to main content

Module exec

Module exec 

Source
Expand description

One exec result as the model reads it.

The command’s stdout and stderr become one text, go through package under the command’s key, and come back as content with the sieve’s account beside it. Every other field of the result (the arm, the exit code, the names the child inherited, what the backlog handed back) stays where the tool put it. This is the one door for the shape: the city and citysim both come through it, so a window the simulator replays is the window the product showed.

Structs§

SieveSite
Where a sieved result’s original goes and what decides the cut: the tee’s site, the run’s filter table, and the run’s history.

Constants§

EXEC_CAP_BYTES
A command result’s byte budget in the window. One value for both callers; the sieve’s floor and stages are the real shrink, this is the ceiling behind them.

Functions§

package_exec
Sieves and packages one exec outcome.