Some frameworks do provide a "state" store somewhere that will be passed around, so I would use that
Some frameworks do provide a "state" store somewhere that will be passed around, so I would use that if possible
IYeah this
IHono calls it context, Fastify calls it state.
IThere's nothing workers-native though I don't think.
HIsn't the "official" one
req.cfLike, as in, they don't guarantee that they won't put new stuff on it, but it will be passed around
IYeah but that's even more likely to be overwritten.
II guess if you name your thing something obscure it'll work, but I can imagine a
req.cf.client some day for some service or another.
Mseem to be experiencing an outage again, with hyperdrive connection latency spikes. is there anyone available who can look into it?
ALet me take a look. Same config ID you'd previously sent?
ALooks like the ID you'd sent previously is not seeing traffic. Please post or DM the one you're seeing issues with. I'm not seeing latency spikes globally, but individual configs certainly could be. Happy to take a look.
MInteresting - I've seen frameworks absolutely encourage storing things on
req between middleware. Otherwise you'd have no option but to laboriously pass around manually a ton of data as function arguments.MExactly.
IAbsolutely, but there's usually a property dedicated towards it.
ILike
ctx
P
ANo, not for Hyperdrive. Not that I've seen or know of.
Podd. I know that they have the same ip pool so i was wondering because for about a minute i had connection timeouts
BSeeing an interesting problem with workers, may or may not be a result of hyperdrive. I have an API implemented in workers with typescript and I'm running React in Pages. Some of my components load 2 different requests simultaneously. Sometimes, works fine, a lot of times, one of the requests receives a connection timeout from the DB. If I disable hyperdrive, the problem goes away. If I stagger the request by a second or two then there is no problem. Is it possible hyperdrive or workers cannot locate a connection in such quick succession? Should I serialize the requests?
Interestingly, I also see the problem locally with wrangler dev. Again, stagger the requests, no issue.
Interestingly, I also see the problem locally with wrangler dev. Again, stagger the requests, no issue.
MIf you’re seeing it in dev - where Hyperdrive’s connection logic isn’t in place - it might be something else. Are you doing something odd with your driver/client code?
BNothing unique and no problems normally. The only issue is if I send off 2 simultaneous connections from react at roughly the same time. I see it in wrangler and I see it in workers production. Using Hono and Kysley. I'll dig a bit more, as of right now, just staggering the requests.
PI think its possible I'm experiencing this as well
Pstarted getting this error a couple days ago
Pthat looks like a bug
Pand i suppose it is
Pbut whats interesting is
PPCONNECT_TIMEOUT?
P its a bug in postgres.js, caused by CONNECTION_TIMEOUTs
PFurthermore, I can corroborate that the issue is solved when hyperdrive is disabled
PI can tell that hyperdrive was properly disabled because requests now take about 200ms longer
AHow interesting. Can you share a code snippet that induces this behavior? How often/reliably does it reproduce for you?
AAside, you should be seeing better caching behavior now, btw, @Ping for toast . How's it looking on your side?
PBy a code snippet, do you mean you're asking for a minimum reproducible example? My configuration is very much like bs_sfalls
- I use solid-start and hyperdrive, and my backend is elysia with hyperdrive.
- The backend is hosted on a separate worker.
- In SSR, two requests are fired simultaneously — one to retrieve data about the current user, and one to fetch the data presented on the page, using service bindings
- This can obviously be triggered by doing a page reload.
- Until said page reload happens, requests work fine
- After n seconds (where n is unknown; greater than 30s and less than 5 minutes?), presumably after hyperdrive disconnects // the worker cools down, it begins working again
PCaching is a lot better — 50% or so
PI also literally just switched db hosts as I thought this would be a good opportunity, so I will test it again to see if it reproduces
AInteresting. We do have some rate limiting in place but it wouldn't be triggered by a single pair of simultaneous requests, and even if it was it would only lock out for a couple hundred ms.
I'm going to have to dig at this a bit. I'll put together a ticket for it
You said this only started within the last week or so?
@bs_sfalls same timeframe for you, just the last week or so?
I'm going to have to dig at this a bit. I'll put together a ticket for it
You said this only started within the last week or so?
@bs_sfalls same timeframe for you, just the last week or so?
Pyup, you can actually see the first time i noticed it
Pright here :)
Pit could have been up to a week tho
PReproduced
PThe reason that it looks like the html has loaded is because of streaming
IYes followed the instructions, using the exact same code as the examples in the documentation. Getting the error 'PostgresError: server requires encryption' when postgres in the Cloudflare worker attempts to set up a connection.
PAny updates on this? If not, would you mind pinging me when there's updates 
, it would be very appreciated
, it would be very appreciatedAWill ping you when we have anything to share on this one. You'd better have toast.
Palways 
Bhi gusy does worker support node-postgres's pg.Pool ? when i building with svelte Cloudflare adapter, i got fs,dns,...etc not supported error
IMake sure you have nodejs_compat enabled in your wrangler.toml.
Icompatibility_flags = ["nodejs_compat"]