starknet 10.6.5 → 10.6.6

package/dist/index.mjs

@@ -7579,6 +7579,8 @@ var WebSocketChannel = class {
       this.reconnectStabilityTimeoutId = null;
     }
     this.userInitiatedClose = true;
+    this.isReconnecting = false;
+    this._rejectRequestQueue("the connection was closed by the user");
     this.websocket.close(code, reason);
   }
   /**
@@ -7652,6 +7654,24 @@ var WebSocketChannel = class {
       this.sendReceive(method, params).then(resolve).catch(reject);
     });
   }
+  /**
+   * Reject every request still waiting in the queue.
+   *
+   * A queued request carries no timeout of its own: the `requestTimeout` timer is only
+   * armed once the request is actually put on the wire. So once the channel reaches a state
+   * where the queue can never be flushed — reconnection gave up, or the user closed the
+   * connection — the queued promises would stay pending forever, and no caller-side timeout
+   * could rescue them. Settling them here is the only way out.
+   */
+  _rejectRequestQueue(reason) {
+    if (this.requestQueue.length === 0) return;
+    const pending = this.requestQueue;
+    this.requestQueue = [];
+    logger.info(`WebSocket: Rejecting ${pending.length} queued request(s). Reason: ${reason}.`);
+    pending.forEach(({ method, reject }) => {
+      reject(new WebSocketNotConnectedError(`Request ${method} was never sent: ${reason}`));
+    });
+  }
   async _restoreSubscriptions() {
     const oldSubscriptions = Array.from(this.activeSubscriptions.values());
     this.activeSubscriptions.clear();
@@ -7695,6 +7715,9 @@ var WebSocketChannel = class {
       if (this.reconnectAttempts >= this.reconnectOptions.retries) {
         logger.error("WebSocket: Maximum reconnection retries reached. Giving up.");
         this.isReconnecting = false;
+        this._rejectRequestQueue(
+          `reconnection gave up after ${this.reconnectOptions.retries} attempts`
+        );
         return;
       }
       this.reconnectAttempts += 1;