Creates the error reported for a dispatch that outlived the bound while the gate had neither settled nor rejected.
The configured chainReadyTimeoutMs bound that fired
OptionalcauseOptionalstackReadonlytimeoutThe bound that fired, in milliseconds.
StaticstackThe 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
Thrown when a delivery held on the ingress behaviour-chain gate (
PipelinedBroker) waits longer than the configuredchainReadyTimeoutMs(default 10 000 ms;0waits forever) for the behaviour chain to open.The gate opens at the end of
onInit; a dispatch still held past the bound meansonInitnever ran to completion — most often a plugin that publishes during its ownregister()while a behaviour factory is configured, which closes a circular wait (publish → delivery → gate →onInit→ theregister()that never returns). The gate itself is left in place, so later dispatches refuse the same way rather than delivering through a partial chain.Since
0.4.0