Skip to content

ProvisionExpiredError

Defined in: packages/client/src/worker/attach-sync-client.ts:243

A provisionSyncWorker that never settled inside its bounded window (provisionExpiryMs, default 60000). The provision’s three ordinary outcomes all depend on the SharedWorker connection being alive — the provision-ack, a storage-declaration refusal, an unconstructible elected engine — so a connection that DIES before any of them (the SharedWorker crashed, its port was never serviced, the elected engine never came up) would otherwise leave the caller pending FOREVER. The deadline settles it loudly instead.

The guarantee is narrow, deliberately: it bounds THIS CALLER’S promise. What becomes of the worker-side create attempt is decided by PLACEMENT, and the two homes differ:

  • SW-direct. The attempt lives in the SharedWorker and is left running (an in-flight store open cannot be safely abandoned — a second open against the same store is an ownership conflict). A later attachSyncClient ADOPTS it if it completed and WAITS on it if it is genuinely stuck; a retried provision re-acks against the SAME attempt, so a second open never starts. A stuck storage open blocks that store whether or not it was ever provisioned, and expiring this promise neither causes nor cures that.
  • Elected. This deadline is ALSO the provision claim’s expiry, so the claim releases here too. When it is the LAST claim on the store’s coordinator, that release runs last-claim retirement (engine-retiringengine-teardown → terminate), taking the elected engine and the attempt inside it — agent termination releases the VFS ownership — and the next attach elects a FRESH engine that opens the store again. An attach that adopted the coordinator BEFORE the expiry holds its own claim, which keeps the engine (and its attempt) alive: the SW-direct adopt-or-wait shape then applies here too.

[pgxsinkit]-prefixed like the repo’s other typed errors so a consumer can instanceof-branch it.

  • Error

new ProvisionExpiredError(storePath, expiryMs): ProvisionExpiredError

Defined in: packages/client/src/worker/attach-sync-client.ts:248

string

number

ProvisionExpiredError

Error.constructor

optional cause?: unknown

Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es2022.error.d.ts:24

The cause of the error.

Error.cause


readonly expiryMs: number

Defined in: packages/client/src/worker/attach-sync-client.ts:247

The window that elapsed without a settlement, in ms (the effective provisionExpiryMs).


message: string

Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1075

Error.message


name: string

Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1074

Error.name


optional stack?: string

Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1076

Error.stack


readonly storePath: string

Defined in: packages/client/src/worker/attach-sync-client.ts:245

The store whose provision expired — the storePath the call was made for.


static stackTraceLimit: number

Defined in: node_modules/.bun/@types+node@26.1.2/node_modules/@types/node/globals.d.ts:67

The 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.

Error.stackTraceLimit

static captureStackTrace(targetObject, constructorOpt?): void

Defined in: node_modules/.bun/@types+node@26.1.2/node_modules/@types/node/globals.d.ts:51

Creates 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();

object

Function

void

Error.captureStackTrace

static captureStackTrace(targetObject, constructorOpt?): void

Defined in: node_modules/.bun/bun-types@1.3.14/node_modules/bun-types/globals.d.ts:1042

Create .stack property on a target object

object

Function

void

Error.captureStackTrace


static isError(error): error is Error

Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.esnext.error.d.ts:21

Indicates whether the argument provided is a built-in Error instance or not.

unknown

error is Error

Error.isError

static isError(value): value is Error

Defined in: node_modules/.bun/bun-types@1.3.14/node_modules/bun-types/globals.d.ts:1037

Check if a value is an instance of Error

unknown

The value to check

value is Error

True if the value is an instance of Error, false otherwise

Error.isError


static prepareStackTrace(err, stackTraces): any

Defined in: node_modules/.bun/@types+node@26.1.2/node_modules/@types/node/globals.d.ts:55

Error

CallSite[]

any

https://v8.dev/docs/stack-trace-api#customizing-stack-traces

Error.prepareStackTrace