Optional ReadonlycauseReadonlydirectoryReadonlyretryableWhether reconnecting and replaying can plausibly clear this failure.
Background maintenance and checkpoint faults are parked and cleared on the next successful batch, so a briefly full, read-only or descriptor-starved filesystem is retryable. Structural corruption and a slot lock taken over by another process are verdicts on the journal itself and are not. The ingress connection lives in the browser-safe layer and cannot reference these classes, so it reads this flag structurally.
OptionalstackStaticstackThe 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
Ownership of the advisory lock could not be re-proved right now. Nothing was taken: reading the owner record is the only heartbeat step that needs a file descriptor, so process-wide descriptor pressure, an
EIO, or an NFSESTALEfails precisely it whilestatandutimeskeep succeeding.Reported separately from QwpReplayStoreLockLostError because the two demand opposite responses. A takeover is terminal; this is transient and self-healing, so it stays retryable: the append backpressure loop parks on it until
appendDeadlineMs, and the reconnect loop retries rather than ending the session. Collapsing them terminated a producer -- permanently, with the transport healthy throughout -- because the host process briefly ran out of descriptors, and blamed a second process that did not exist.