Error: Cannot perform I/O on behalf of a different request

Hi Everyone

I have a project where i'm using sveltekit but i had a problem where when clicking back or forward in the browser is causing internal error 500? after i get the internal error 500 i try to refresh (ctrl + r) it went normal.

I have 2 webapps that have this issues, and weirdly its happening in the production build that i already deploy in the cloudflare pages, dev and local build environment is fine.

i see the logs and i got

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.

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.

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.

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.

alka_99OP•2/18/24, 8:57 AM

bump. this only happening in cloudflare pages.

logs is attached

alka_99OP•2/18/24, 1:42 PM

anyone can help?

alka_99OP•2/18/24, 3:24 PM

looking at log i get error

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.

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.

Cyb3r-Jak3•2/18/24, 3:34 PM

That typically means a request was in the global scope was tried to be handled by a different request

CCyb3r-Jak3 That typically means a request was in the global scope was tried to be handled b...

alka_99OP•2/18/24, 3:34 PM

do you have any idea where i should start debugging then? I'm new in programming world

Aalka_99 do you have any idea where i should start debugging then? I'm new in programming...

Cyb3r-Jak3•2/18/24, 3:36 PM

Can you share what your code looks like?

alka_99OP•2/18/24, 3:41 PM

i can deploy it in stackblitz give me a moment

Cyb3r-Jak3•2/18/24, 3:43 PM

That error typically means that sveltekit is doing something that it shouldn't be so might be worth asking that community as well

alka_99OP•2/18/24, 3:50 PM

@Cyb3r-Jok3 i also asking sveltekit community, but i haven't get any feedback yet

Cyb3r-Jak3•2/18/24, 3:57 PM

I am seeing

[Error: Cannot subscribe to 'page' store on the server outside of a Svelte component, as it is bound to the current request via component context. This prevents state from leaking between users.For more information, see https://kit.svelte.dev/docs/state-management#avoid-shared-state-on-the-server]

[Error: Cannot subscribe to 'page' store on the server outside of a Svelte component, as it is bound to the current request via component context. This prevents state from leaking between users.For more information, see https://kit.svelte.dev/docs/state-management#avoid-shared-state-on-the-server]

Seems similar to the cloudflare error

alka_99OP•2/18/24, 3:57 PM

i think that's different error

alka_99OP•2/18/24, 3:58 PM

it is state management for sveltekit, i might miss that one

Cyb3r-Jak3•2/18/24, 4:01 PM

Ah only thing I could think of with it. Don't know Svelte well so hopefully someone who does will know what the cause is

alka_99OP•2/18/24, 4:02 PM

@Cyb3r-Jok3 thank you for your hands :MeowHeartCloudflare:

alka_99OP•2/18/24, 4:11 PM

i didn't get with the global scope can you elaborate more? @Cyb3r-Jok3

alka_99OP•2/22/24, 5:40 AM

bump.

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.

[Error: Cannot subscribe to 'page' store on the server outside of a Svelte component, as it is bound to the current request via component context. This prevents state from leaking between users.For more information, see https://kit.svelte.dev/docs/state-management#avoid-shared-state-on-the-server]

Error: Cannot perform I/O on behalf of a different request

Similar Threads

Similar Threads

Similar Threads