Expand description
Typed, operator-tunable VM-scoped runtime limits.
VmLimits is the single home for runtime bounds that operators may tune through the typed
create-VM JSON config. Every field is a concrete value (not Option): the Default impls own
the numbers and they are byte-identical to the historical hardcoded constants, so behavior is
unchanged unless an operator overrides a config field.
Structs§
- AcpLimits
- Http
Limits - JsRuntime
Limits - Plugin
Limits - Python
Limits - Tool
Limits - VmLimits
- All operator-tunable VM-scoped limits. Fields are concrete values; the
Defaultimpls own the numbers and equal today’s hardcoded constants, so unset operator config leaves behavior unchanged. - Wasm
Limits
Constants§
- DEFAULT_
ACP_ MAX_ READ_ LINE_ BYTES - DEFAULT_
ACP_ STDOUT_ BUFFER_ BYTE_ LIMIT - DEFAULT_
JS_ CAPTURED_ OUTPUT_ LIMIT_ BYTES - DEFAULT_
JS_ EVENT_ PAYLOAD_ LIMIT_ BYTES - DEFAULT_
JS_ STDIN_ BUFFER_ LIMIT_ BYTES - DEFAULT_
MAX_ FETCH_ RESPONSE_ BYTES - Default cap on
vm.fetch()buffered response bodies. Historically aliased to the wire frame cap; decoupled here but still validated to stay within the negotiated frame budget. - DEFAULT_
PYTHON_ EXECUTION_ TIMEOUT_ MS - DEFAULT_
PYTHON_ OUTPUT_ BUFFER_ MAX_ BYTES - DEFAULT_
PYTHON_ VFS_ RPC_ TIMEOUT_ MS - DEFAULT_
TOOL_ TIMEOUT_ MS - DEFAULT_
V8_ IPC_ MAX_ FRAME_ BYTES - DEFAULT_
WASM_ CAPTURED_ OUTPUT_ LIMIT_ BYTES - DEFAULT_
WASM_ MAX_ MODULE_ FILE_ BYTES - DEFAULT_
WASM_ SYNC_ READ_ LIMIT_ BYTES - MAX_
PERSISTED_ MANIFEST_ BYTES - MAX_
PERSISTED_ MANIFEST_ FILE_ BYTES - MAX_
REGISTERED_ TOOLKITS - MAX_
REGISTERED_ TOOLS_ PER_ VM - MAX_
TOOLS_ PER_ TOOLKIT - MAX_
TOOL_ EXAMPLES_ PER_ TOOL - MAX_
TOOL_ EXAMPLE_ INPUT_ BYTES - MAX_
TOOL_ SCHEMA_ BYTES - MAX_
TOOL_ TIMEOUT_ MS