OptionalcauseReadonlykindDiscriminated tag for exhaustive matching.
ReadonlynodeOptionalstackReadonlytimeStaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
Raised by
readAt(node, t)/snapshotAt(t)on the WASM (rust-ssot) engine when a RETAINED historical row names a container input whose value the engine holds only as a structural content-hash marker, and the value can no longer be recovered host-side.Remarks
The wasm engine stores a container input (Array / Object) as a deterministic content-hash marker rather than a full copy — its cutoff /
State::hashoperate over the hash, and the real value is served from the host-side per-NodeId value cache, which holds only the CURRENT reference. A read-at-time therefore recovers a container value only while the queried row is still the live one; once the input's reference has changed, the historical container value is genuinely gone (the pure-TS floor, which retains full snapshot history, still returns it — a documented engine divergence, and as of 0.5.0 one no adopter can reach from this package:createCausl()no longer has a floor to select).Rather than hand the adopter the internal content-hash sentinel where a
Twas promised (silent type corruption), the engine fails LOUD with this typed error. It is the honest "the container's history was not retained" arm, symmetric to theevictedarm's honesty about bounded retention — distinct because eviction is a whole-window bound, whereas this names a per-value residency limitation of content-hash storage.Param: nodeId
Id of the container input whose historical value is gone.
Param: time
The GraphTime the unrecoverable value was requested at.