Is this a Worker/Wrangler/Hyperdrive bug? Request succeeds but then errors on refresh
I have a weird situation whereby an endpoint hosted on CF Workers successfully returns a response. But if I hit refresh soon after (within a couple of seconds) I then get a CF error:
The error makes no sense to me because if the promise could not "possible ever resolve", then it wouldn't have given me a 200 status with output the first time. The problem is only on refresh.
This happens only with endpoints that talk to Hyperdrive. A simple endpoint that outputs a static response does not exhibit this problem, not matter how many times, or how quick, I hit refresh.
I'm using Itty Router, and I cannot see anything in my code that would point to a hanging promise or anything like that - I'm using Itty as advertised.
Thank you.
3 Replies
do you happen to reuse the client that you create using hyperdrive between requests? That's my first guess, since it specifically mentions that it will only be valid during the request where you get the credentials
PurpleBlob, you're a genius. I was indeed doing that. I've been adapting my app from Express use, and handling DB pools manually, so I hadn't properly adapted this part. Thank you!
happy to help 