ex0ns Posts - Answer Overflow

ex0ns

Explore posts from servers

•Created by ex0ns on 3/5/2025 in #help

Closing resources and streaming response

I'm running Hono on node.js and I had a bug the other day, we added an endpoint to our API that was streaming the response back to the client, however we got some weird connection error to our database while the stream was running. In one of our middleware we instanciate a postgres.js connection to the database, and we use this connection to generate streaming data to the client, however to avoid leaking connection we explicitly close the connection at the end of the middleware (I know there are some ways to re-use connection using pooling, but this is not the point here (for info, we are dynamically connecting to many different database depending on where the request is coming from, so we can't easily implement a pooling mecanism on this server). Of course the middleware is running as soon as the response (i.e the beginning of the stream) is send back to the user, which trigger the cleaning of the resource, and a failure of the generator to produce more results in the stream. The following reproducer explains the problems quite well I think:

34 replies

WWindmill

•Created by ex0ns on 5/23/2024 in #help

typescript client in cloudflare workers

I was using wmill typescript client from my cloudflare workers but it stopped working today:

✘ [ERROR] service core:user:my-app: Uncaught ReferenceError: process is not defined
cloudflare-backend:dev: 
cloudflare-backend:dev:     at null.<anonymous> (index.js:649:9) in getEnv
cloudflare-backend:dev:     at null.<anonymous> (index.js:653:32) in
cloudflare-backend:dev:   ../../node_modules/.pnpm/[email protected]/node_modules/windmill-client/dist/core/OpenAPI.js
cloudflare-backend:dev:     at null.<anonymous> (index.js:11:50) in __require
cloudflare-backend:dev:     at null.<anonymous> (index.js:7960:21) in
cloudflare-backend:dev:   ../../node_modules/.pnpm/[email protected]/node_modules/windmill-client/dist/index.js
cloudflare-backend:dev:     at null.<anonymous> (index.js:11:50) in __require
cloudflare-backend:dev:     at null.<anonymous> (index.js:31929:21)
cloudflare-backend:dev:

✘ [ERROR] service core:user:my-app: Uncaught ReferenceError: process is not defined
cloudflare-backend:dev: 
cloudflare-backend:dev:     at null.<anonymous> (index.js:649:9) in getEnv
cloudflare-backend:dev:     at null.<anonymous> (index.js:653:32) in
cloudflare-backend:dev:   ../../node_modules/.pnpm/[email protected]/node_modules/windmill-client/dist/core/OpenAPI.js
cloudflare-backend:dev:     at null.<anonymous> (index.js:11:50) in __require
cloudflare-backend:dev:     at null.<anonymous> (index.js:7960:21) in
cloudflare-backend:dev:   ../../node_modules/.pnpm/[email protected]/node_modules/windmill-client/dist/index.js
cloudflare-backend:dev:     at null.<anonymous> (index.js:11:50) in __require
cloudflare-backend:dev:     at null.<anonymous> (index.js:31929:21)
cloudflare-backend:dev:

I think that the commit that broke this is https://github.com/windmill-labs/windmill/pull/3714/files#diff-13bcd4e9fc2a785250e31b9122dbedeacc95fe47601feeb1169a0da8c84917a6R8 Before this commit, the lookup in the env was not performed in case the setClient method was called, and in CF Workers, process is not something that exists Do you have a workaround to make wmill typescript client work from Cloudflare workers ?

10 replies

Gaming

Programming