GeezerVison

Fixes #283

Problem

On the WebSocket transport, transportCommands waits for the socket.io ack of GET /v2/weblite/sql. If the socket disconnects while a query is in flight (for example when the gateway closes the connection because the request exceeds its maxHttpBufferSize, or on a ping timeout):

• the ack never fires;
• the disconnect handler only calls the connect callback, which already ran on connect, so the error is logged (SQLiteCloudConnection.connect - error connecting … Disconnected) but never reaches the command;
• close() clears the operations queue, so nothing else settles it;
• unlike the TLS transport there is no timeout to fall back on.

The result is a db.sql(...) promise that never resolves nor rejects.

A side effect of calling the connect callback a second time is that the base connect() wrapper calls the queue's done twice, and Database receives a second callback for the same connection.

Fix (src/drivers/connection-ws.ts)

• Each command registers itself in pendingCommands until its ack arrives. Its callback is guarded so it runs exactly once (response, timeout or connection loss).
• disconnect, connect_error and error close the socket and fail every pending command with the same error the connect callback used to receive (ERR_CONNECTION_ENDED with the socket.io reason as cause, the attachment limit error, etc.).
• close() fails pending commands with ERR_CONNECTION_CLOSED.
• The connect callback is called only once, for the outcome of the connection attempt (same as the TLS transport, where later errors go to the command in progress).
• config.timeout (default 300 s) now applies to WebSocket requests too: when it elapses the command fails with ERR_CONNECTION_TIMEOUT and a late ack is ignored. The connection stays open, since the gateway handles every request independently.

The request size limit itself is a gateway configuration and is out of scope here: with this change, whatever the limit is, the driver reports an error instead of hanging.

Testing

New unit tests in test/connection-ws-unit.test.ts (mocked socket.io):

• the command in flight fails with ERR_CONNECTION_ENDED on disconnect, and the connect callback is not called again;
• a disconnect before connect is still reported to the connect callback;
• close() fails the command in flight;
• the command fails after timeout and a late response is ignored;
• a completed command is not affected by a later disconnect or timer.

Three of these fail on main and pass with the fix.

Manual check against the staging gateway, sending SELECT length(X'…') payloads above its message size limit:

connection-ws, blob-transport, database, statement and utilities test suites pass.