Skip to main content

Module exec

Module exec 

Source
Expand description

Exec-related protocol message payloads.

Structs§

ExecExited
Notification that a command has exited.
ExecFailed
Notification that a command failed to start (the user’s program never got to run). Distinct from ExecExited, which means the process ran and reported an exit code.
ExecLimits
Runtime-owned execution policy advertised in Ready. Effective policy shared by every execution in one sandbox.
ExecOutputAck
Acknowledges cumulative output consumed by the SDK, including per-chunk overhead.
ExecRequest
Request to execute a command in the guest.
ExecResize
Request to resize the PTY of a running command.
ExecRlimit
A POSIX resource limit to apply to a spawned process.
ExecSignal
Request to send a signal to a running command.
ExecStarted
Confirmation that a command has been started.
ExecStderr
Stderr data from a running command.
ExecStdin
Stdin data sent to a running command.
ExecStdinAck
Acknowledges cumulative bytes written into the child’s stdin pipe.
ExecStdinError
Notification that an ExecStdin write to the child’s stdin failed. The most common cause is the child closing its read end (EPIPE); the session is otherwise alive and may still produce output and an exit code, so this is delivered as a non-terminal event.
ExecStdout
Stdout data from a running command.

Enums§

ExecFailureKind
Coarse classification of an ExecFailed cause. The CLI’s stage-to-hint mapper keys off this; the SDK exposes it directly for programmatic consumers.
RlimitResource
POSIX resource limit identifiers.

Constants§

EXEC_OUTPUT_EVENT_OVERHEAD
Window charge for each output chunk, bounding even very small writes. Memory-accounting charge in addition to each output payload.
MAX_EXEC_CONTROL_BYTES
Maximum encoded execution acknowledgement, signal or resize envelope.