You need to add this compat flag

ah I need

--experimental-local

someone hacked me

they say tehy wanna dox me

that's good

with this link i clicked it then it showed my ip and adress

its not good

getting same error 😦

Is your wrangler version up to date?

let me update

In the documentation regarding simultaneous open connections, it says

Once a Worker has six connections open, it can still attempt to open additional connections. However, these attempts are put in a pending queue

however, on an *unbound * scheduledEvent worker I'm testing, I'm seeing that anything over 6 connections triggers failure in the log saying that the Request limit was reached. I thought that exceeding this limit only put further requests into first-in-last-out queue and didn't interrupt the program flow?

The request limit being reached sounds like you're reaching the cap of total requests (1000 for unbound), rather than the cap of outgoing connections 🤔

Further context: unbound worker, total of 330 fetch requests within, executed by cron, locally works, production fails with a log message.

That's what I thought so I debugged it further. Only the expected 330 fetch requests being executed. Locally this works in unbound mode. On production it fails. If I reduce the fetch requests to 5 and redeploy, it seems to not fail with the error.

we run 10 at the same time in production with unbounded no problem

The error seems to be tied to the simultaneous open connection limit and not the request limit.

I'm stuffing all of the requests into a single promise.all and not batching them... that was my next step but I want to validate that I'm not misunderstanding the documentation around simultaneous open connections before I just through hoops.

yeah we are doing the same and no issue here

Curious.

btw I updated wrangler and getting some weird errors...

workerd/jsg/util.c++:427: error: e = kj/compat/tls.c++:215: failed: TLS peer's certificate is not trusted; reason = unable to get local issuer certificate

had to turn off my VPN... it worked fine with the old version 😦

man I'm getting all sorts of weird errors with this new version 😦

Looks like your VPN does some traffic interception, which requires a cert that

workerd

can't read.

this is with my VPN off now

it errored out before it got to this code before

it is when calling Supabase to validate a JWT

You should be able to use

--compatibility-flags

without

--experimental-local

okay I'll try it, the docs said to use it

alright we are getting somewhere