Describe the bug Using surrealdb.js on Cloudflare Pages platform w

While running into the issue with DevTools, heres what you get: <div class="snippe

Bug: CF Pages SSR with SurrealJS fails about surrealdb.js HOT 2 OPEN

itsezc commented on June 13, 2024 1

Bug: CF Pages SSR with SurrealJS fails

from surrealdb.js.

Comments (2)

itsezc commented on June 13, 2024

While running into the issue with DevTools, heres what you get:

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.
Uncaught (in response) Error: The script will never generate a response.

Upon debugging further:

Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance.
    at _SurrealSocket.send (SurrealSocket.ts:133:12)
#options.hooks.handleError @ index.js:2903
handle_error_and_jsonify @ index.js:174
render_page @ index.js:2090

from surrealdb.js.

raymonddaikon commented on June 13, 2024

I'm having the same issue with CloudFlare workers (via Partykit). Making a db call using the client library hangs indefinitely. I'm not sure whether or not it's an issue with serialization or the ws protocol. A reproduction can be created with a starter template and adding an onStart surrealdb.js call function

  async onStart() {
    this.surrealClient = new Surreal()
    await this.surrealClient.connect(this.room.env.SURREALDB_URL as string, {
      auth: {
        namespace: 'ns',
        database: 'db',
        username: 'root'
        password: 'root',
        scope: undefined,
      },
    })
    await this.surrealClient.query()
  }