I honestly have no idea how would you debug such error because I've had it too in the past and it is

DD Trombett I honestly have no idea how would you debug such error because I've had it too i...

J

johtso•12/14/24, 6:35 PM

all I get is

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

⎔ Starting local server...
✘ [ERROR] service core:user:email-sender: Uncaught Error: Top-level await in module is unsettled.

when running

workers dev

workers dev

workers dev

workers dev

J

johtso•12/14/24, 6:36 PM

when trying to deploy I get

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/email-sender-prod/versions) failed.

  The uploaded script has no registered event handlers. [code: 10068]

Jjohtso when trying to deploy I get ``` ✘ [ERROR] A request to the Cloudflare API (/acco...

D

D TrombettOP•12/14/24, 6:46 PM

Uh, wait, does Cloudflare use commonjs in production? It's strange that you don't get the same error

J

johtso•12/14/24, 7:26 PM

ok, finally found the culprit after a whole day of commenting out code

J

johtso•12/14/24, 7:26 PM

and yes, it was a top level await that I'd added while testing things

J

johtso•12/14/24, 7:26 PM

I wonder if there's a more efficient way to find the offending code in a situation like this?

Jjohtso I wonder if there's a more efficient way to find the offending code in a situati...

H

Hello, I’m Allie!•12/14/24, 7:36 PM

A linter rule maybe?

J

johtso•12/14/24, 7:36 PM

yeah, I definitely need to set up some linting and typescript error checking for this project

J

johtso•12/14/24, 7:37 PM

also a lesson to commit early and often, the smaller the diff between your last working version and your current code, the less places there are for a new issue to hide and the fewer potential red herrings

J

johtso•12/14/24, 7:38 PM

don't do a big dependency update and write some new code without committing in between

M

MrBithles•12/15/24, 8:02 AM

For a local worker with remote flag that is setup with RPC (WorkerEntrypoint) and using browser render with queues is it possible to call worker's fetch locally because I only get 500 response and no logs to why. (Need to have remote flag because browser render doesn't work on local wrangler)

Worker code snippet

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

export default class Entrypoint extends WorkerEntrypoint {
  async fetch(req: Request) {
    console.log('fetch'); // this is not logged
    return new Response('ok');
  }

  async queue(batch: MessageBatch<Message>) {
    // this runs on deployed workers fine
  }
}

Calling worker via localhost

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

curl -X POST http://localhost:8787

Logs from wrangler dev, but I don't see my console log in fetch

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

[wrangler:inf] POST / 500 Internal Server Error

SShayan I have a CRON worker (Worker A) that fetches my database and gets a list of ID's...

H

Hello, I’m Allie!•12/15/24, 7:35 PM

You can use a Service Binding instead of fetching.

Cloudflare Docs

Service bindings - Runtime APIs · Cloudflare Workers docs

Facilitate Worker-to-Worker communication.

W

Walshy•12/15/24, 10:32 PM

https://en.m.wikipedia.org/wiki/CPU_time
tldr is that its compute time. If you're waiting for a fetch call for example, that is not counted.

W

Walshy•12/16/24, 12:43 AM

Yes

W

Walshy•12/16/24, 3:18 AM

i assume you're on free plan

W

Walshy•12/16/24, 3:20 AM

if so, yeah the limit is 10ms so it will cut you off. we don't have a hard cut off at 10ms though, we allow you to go higher (to account for spikes, variance or what have you). if you consistently are higher then you'll see your cpu time exceeded

W

Walshy•12/16/24, 3:20 AM

yes

W

Walshy•12/16/24, 3:25 AM

https://developers.cloudflare.com/workers/platform/limits/#worker-limits
https://developers.cloudflare.com/workers/platform/limits/#cpu-time

W

Walshy•12/16/24, 3:26 AM

Scheduled Workers (Cron Triggers) have different limits on CPU time based on the schedule interval. When the schedule interval is less than 1 hour, a Scheduled Worker may run for up to 30 seconds. When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.

R

rdutton•12/16/24, 3:33 AM

Looking at Shayan's code for Worker A, are the fetches to Worker B guaranteed to occur given there is no 'await' before the worker returns it's response?

L

Lulu•12/16/24, 5:43 AM

I looked at the compatibility matrix for workers / pages, and the features I need are supported in both. At this point would there be any advantage in using one over the other? I know the Frameworks feature is still in beta for Workers but that doesn't matter to me atm.

LLulu I looked at the compatibility matrix for workers / pages, and the features I nee...

H

Hello, I’m Allie!•12/16/24, 5:46 AM

From a roadmap perspective, Workers are the future. While they don’t quite have all of the features you might need for website hosting like Pages do, they are the first to get new features when they launch, and some new features may only launch on Workers

R

rdutton•12/16/24, 6:00 AM

For me the missing pieces from Pages are logging and queue consumption. Now that Workers have static assets and noting the above comment, I might try to migrate some projects from Pages to Workers.

S

sathoro•12/16/24, 6:40 AM

we use both. frontend on Pages, backend on Workers. it is actually nice to be able to deploy them separately

A

anurag•12/16/24, 7:44 AM

Hi, Team
how do you attach more info to the worker request? We're getting a lot of clients disconnected and 429 and I want to investigate why but there's no information in the worker logs.

Would really appreciate any recommendation on how to investigate this

A

anurag•12/16/24, 7:45 AM

I want to attach user id to the worker metadata

Aanurag Hi, Team how do you attach more info to the worker request? We're getting a lot ...

M

masd4•12/16/24, 7:48 AM

check the 3rd paragraph here and tell us if you see this anti abuse mechanism triggered? https://developers.cloudflare.com/workers/platform/limits/#request

Mmasd4 check the 3rd paragraph here and tell us if you see this anti abuse mechanism tr...

A

anurag•12/16/24, 7:52 AM

I don't see anything

Mmasd4 check the 3rd paragraph here and tell us if you see this anti abuse mechanism tr...

A

anurag•12/16/24, 7:56 AM

I don't know if it's the correct way to add metadata but AI suggested it

Aanurag Hi, Team how do you attach more info to the worker request? We're getting a lot ...

A

anurag•12/16/24, 7:56 AM

Also I have no idea what this log mean

J

JeffL•12/16/24, 6:50 PM

Hey all,
(I'm experienced with workers, but I think this is a bit of an undocumented edge case).

I've put a worker in front of a site hosted by Beehiiv (a CMS). It seems that Beehiiv uses workers as a service provider, the beehiiv worker runs first, and 404s the routes I want to serve before my worker can run. Is there a way to make my worker run earlier, and take priority over theirs?

JJeffL Hey all, (I'm experienced with workers, but I think this is a bit of an undocume...

H

Hello, I’m Allie!•12/16/24, 6:52 PM

?pings

S

SuperHelpflare•12/16/24, 6:52 PM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

HHello, I’m Allie!?pings

J

JeffL•12/16/24, 6:55 PM

Sorry.

R

R.Thompson•12/16/24, 9:02 PM

This may be the wrong place to ask, but how long does it usually take to reinstall the Github App in Github? I was running into an error and Cloudflare prompted me to uninstall and reinstall, but it's saying I put in a "request" to reinstall the app.

R

R.Thompson•12/16/24, 11:43 PM

It turns out it sent an email to the admin account and I hadn't realized it. It should be/usually is pretty instant.

A

Ashley•12/17/24, 3:44 AM

Hey all,
We are testing out the beta rate limiting feature for Cloudflare workers and it appears that it is somewhat broken. I understand that this is eventually consistent, but it appears that this consistency is never achieved.

For the sake of testing, I have set the threshold very low - 1 within 60 seconds.

I then run a tool which sends HTTP requests to the endpoint in question and returns whether it was rate limited. I have uploaded the screenshots which shows the result of running each request sequentially. Bearing in mind the requests start at 1:39:21 PM and finishes at 1:39:45 PM which IMO is a substantial amount of time given for things to become "consistent" especially given the limit being "1".

Is there some gotchas I am unaware of? This seems frankly bizarre. The key is based on my IPV6 address and I've ensured that this remains consistent for each request.

I honestly have no idea how would you debug such error because I've had it too in the past and it is

Similar Threads

Similar Threads

Similar Threads