Sébastien Morel Posts - Answer Overflow

Sébastien Morel

Explore posts from servers

•Created by Sébastien Morel on 3/21/2025 in #help

Invalid state: ReadableStream is already closed

Hello here, I am starting to suspect something odd in @hono/node-server We have random ReadableStream is already closed in the app, everything is try/catch but anyway it crashes the container. We are also using GraphQL Yoga, I found out about this: https://github.com/honojs/node-server/issues/77 But I hesitate to do that because GraphQL Yoga is using @whatwg-node/fetch which is supposed to be a good abstraction. the full trace is:

node:internal/webstreams/readablestream:1162
throw new ERR_INVALID_STATE.TypeError('ReadableStream is already closed');
^
TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
at ReadableByteStreamController.close (node:internal/webstreams/readablestream:1162:13)
at node:internal/deps/undici/undici:1480:28
at node:internal/process/task_queues:151:7
at AsyncResource.runInAsyncScope (node:async_hooks:211:14)
at AsyncResource.runMicrotask (node:internal/process/task_queues:148:8)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
code: 'ERR_INVALID_STATE'
}
Node.js v22.13.1

node:internal/webstreams/readablestream:1162
throw new ERR_INVALID_STATE.TypeError('ReadableStream is already closed');
^
TypeError [ERR_INVALID_STATE]: Invalid state: ReadableStream is already closed
at ReadableByteStreamController.close (node:internal/webstreams/readablestream:1162:13)
at node:internal/deps/undici/undici:1480:28
at node:internal/process/task_queues:151:7
at AsyncResource.runInAsyncScope (node:async_hooks:211:14)
at AsyncResource.runMicrotask (node:internal/process/task_queues:148:8)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
code: 'ERR_INVALID_STATE'
}
Node.js v22.13.1

Of course I don't reproduce easily, it happens randomly Any idea? to identify the problem better?

26 replies

CDCloudflare Developers

•Created by Sébastien Morel on 12/27/2023 in #workers-help

Within worker DNS resolution is failing

Hello, I am pretty confident that my worker when it is reached through its custom domain. Y.Z.com is unable to resolve X.Z.com. - Zone is not entirely managed by Cloudflare (partial CNAME setup) - Y.Z.com is reachable and worker is running correctly. (just DNS resolution is broken) - X.Z.com is managed on AWS - when reached via it's worker.dev route, DNS resolution is working. I have logs and proofs of all that. Any help? I can't be the only one with that error? Either I do something weird or it's a bug somewhere. Thanks This doc says it should work: https://developers.cloudflare.com/workers/configuration/routing/custom-domains/#:~:text=On%20the%20same%20zone%2C%20if,succeed%20without%20a%20service%20binding

27 replies

CDCloudflare Developers

•Created by Sébastien Morel on 12/19/2023 in #workers-help

Request to URL on the same zone but in CNAME configuration

Hello, I have a weird behavior that I have an hard time debugging. I reach out my worker via my custom domain, this worker is actually doing a fetch to another endpoint on a different domain but same zone. like Worker is: xxxx.plop.com and I fetch from this worker to yyyy.plop.com And when I do that the fetch is clearly not working all the time.. like a weird resolving issue. If I access the worker from the route "worker.dev" it's working 100% i have plenty of debug the fetch is just empty OR sometime it says: "Invalid Link" Any hint ? or way to debug more? Thanks

9 replies

Gaming

Programming