Optionalmessage: stringOptionalmessage: stringOptionaloptions: ErrorOptionsOptionalcauseOptionalstackStaticstackThe 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
A failure that rests on data the backend leading the attempt served.
Four requests decide the domain refusals the walk can raise: the reveal's tx hex, its status, its merkle proof, and the terminal coinbase's status, whose block_height is the height that places the traced position against the subsidy boundary.
fetchSatIdentitymakes them against the leading member alone instead of through the pool: a refusal recorded under a backend's name has to rest on data that backend served itself.The class covers a phase, not a request list. Any failure raised while the build assembles from lead-served data, from the reveal fetch through the reveal hop's assembly, prev-tx coverage and start-position derivation, and again through the terminal coinbase hop's assembly, is one member's failure, whether the request itself failed or the value it returned did: an unconfirmed status, a missing envelope, a named prev-tx output that does not exist. The wrapper records it as that member's cause and leads the next attempt with the next member. The recordable refusal classes,
SatPositionError, and the terminalEnvelopeIndexUnprovenErrorpass through the span unwrapped, since each already has its own arm in the loop. Pool exhaustion on a pooled request outside the span still ends the whole build, and the loop reads that off the class rather than off the position:PooledEsploraBackend.runraisesPoolExhaustedError, which means every member failed the request. A content failure outside the span is caught outsiderun, so it is one attempt's bad bytes and rotates.