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-retiring→engine-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.
Extends
Section titled “Extends”Error
Constructors
Section titled “Constructors”Constructor
Section titled “Constructor”new ProvisionExpiredError(
storePath,expiryMs):ProvisionExpiredError
Defined in: packages/client/src/worker/attach-sync-client.ts:248
Parameters
Section titled “Parameters”storePath
Section titled “storePath”string
expiryMs
Section titled “expiryMs”number
Returns
Section titled “Returns”ProvisionExpiredError
Overrides
Section titled “Overrides”Error.constructor
Properties
Section titled “Properties”cause?
Section titled “cause?”
optionalcause?: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.
Inherited from
Section titled “Inherited from”Error.cause
expiryMs
Section titled “expiryMs”
readonlyexpiryMs: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
Section titled “message”message:
string
Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1075
Inherited from
Section titled “Inherited from”Error.message
name:
string
Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1074
Inherited from
Section titled “Inherited from”Error.name
stack?
Section titled “stack?”
optionalstack?:string
Defined in: node_modules/.bun/typescript@6.0.3/node_modules/typescript/lib/lib.es5.d.ts:1076
Inherited from
Section titled “Inherited from”Error.stack
storePath
Section titled “storePath”
readonlystorePath:string
Defined in: packages/client/src/worker/attach-sync-client.ts:245
The store whose provision expired — the storePath the call was made for.
stackTraceLimit
Section titled “stackTraceLimit”
staticstackTraceLimit: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.
Inherited from
Section titled “Inherited from”Error.stackTraceLimit
Methods
Section titled “Methods”captureStackTrace()
Section titled “captureStackTrace()”Call Signature
Section titled “Call Signature”
staticcaptureStackTrace(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();Parameters
Section titled “Parameters”targetObject
Section titled “targetObject”object
constructorOpt?
Section titled “constructorOpt?”Function
Returns
Section titled “Returns”void
Inherited from
Section titled “Inherited from”Error.captureStackTrace
Call Signature
Section titled “Call Signature”
staticcaptureStackTrace(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
Parameters
Section titled “Parameters”targetObject
Section titled “targetObject”object
constructorOpt?
Section titled “constructorOpt?”Function
Returns
Section titled “Returns”void
Inherited from
Section titled “Inherited from”Error.captureStackTrace
isError()
Section titled “isError()”Call Signature
Section titled “Call Signature”
staticisError(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.
Parameters
Section titled “Parameters”unknown
Returns
Section titled “Returns”error is Error
Inherited from
Section titled “Inherited from”Error.isError
Call Signature
Section titled “Call Signature”
staticisError(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
Parameters
Section titled “Parameters”unknown
The value to check
Returns
Section titled “Returns”value is Error
True if the value is an instance of Error, false otherwise
Inherited from
Section titled “Inherited from”Error.isError
prepareStackTrace()
Section titled “prepareStackTrace()”
staticprepareStackTrace(err,stackTraces):any
Defined in: node_modules/.bun/@types+node@26.1.2/node_modules/@types/node/globals.d.ts:55
Parameters
Section titled “Parameters”Error
stackTraces
Section titled “stackTraces”CallSite[]
Returns
Section titled “Returns”any
https://v8.dev/docs/stack-trace-api#customizing-stack-traces
Inherited from
Section titled “Inherited from”Error.prepareStackTrace