Does anyone know if there are any stats around parse times for workers as they get larger? Just inte
Does anyone know if there are any stats around parse times for workers as they get larger? Just interested is there a tipping point or random stats
HParsing time should generally never be high enough to be noticeable, though startup time does sometimes get high enough to crash the Worker
Smy worker reports the wrong time, somehow, if i use toLocaleString.
for timestamp 1720179195419 i should get, with locale "de-DE", something like 13:33, but it's 11:33 in my worker
for timestamp 1720179195419 i should get, with locale "de-DE", something like 13:33, but it's 11:33 in my worker
Spls tell me i dont have to use the intl api
Si have to use the intl api
Cbumping this for anyone who is searching for details on "consuming from multiple queues in a single worker"
VThe rate limit binding doesn't seem to work very well, i know it's in beta but i can get a lot more than the limit through before it starts to return false.
I have a remix pages app, that binds to a service worker that binds to a ratelimit to get around pages not working with rate limits directly i wonder if that has anything to do with it or if that's the general experience. (limit 3, period 60)
I have a remix pages app, that binds to a service worker that binds to a ratelimit to get around pages not working with rate limits directly i wonder if that has anything to do with it or if that's the general experience. (limit 3, period 60)
Mdo workers literally just not work now?
Mwith wrangler
AHas there been any further news about (Durable) Workflows that was announced in the Developer Week in April?
CWhat do you mean by not work?
Ohey is it just me or was CORS removed from Workers settings?
KI don't recall CORS ever being a Workers setting :meowthinking:
OYeah come to think of it - maybe it was R2 or something like that?
OEither way, getting CORS responses on a worker request
Ostrict-origin-when-cross-origin
OI've got hono implemented with Cors
Oapp.use('/api/*', cors())
BHow can I send a message reply from an application command using my Discord Bot which runs using a worker to a specific channel? i.e. as part of the application command I ask for the parameter of a channel to be given, and I want the bot to then submit a response in that given channel.
BHey there.
Is there a way to perform a differential update of worker settings?
For example, I'd like to dynamically bind a setting like so:
However, this method overrides any previously set bindings. Retrieving all current bindings and adding a new one is another approach, but this will eventually fail due to the max body size limit, so I'm looking for another way of doing this and/or new ideas.
Is there a way to perform a differential update of worker settings?
For example, I'd like to dynamically bind a setting like so:
However, this method overrides any previously set bindings. Retrieving all current bindings and adding a new one is another approach, but this will eventually fail due to the max body size limit, so I'm looking for another way of doing this and/or new ideas.
HI think that is the solution, for now anyway. You would also still hit the size limit, because there is a max size limit for bindings(I think it is 1 MB)
BI see. Thanks.
BI guess another approach would be querying D1 via the REST API (https://developers.cloudflare.com/api/operations/cloudflare-d1-raw-database-query).
HYes, though note that this can be much slower
BThat's what I was afraid of.
BI really don't want to create a worker-d1 pair for every tenant, so ... back to the drawing board.
BTo follow up on this, is it even possible? Or can the bot only respond in the text channel where the application command was triggered from?
HIf your bot has message send permissions, then yes
Ujust double checking, ctx.waitUntil executes the promise after the worker returns, right?
Uhmm
Uis there a way to make it so the code executes after it returns?
Ulike a promise for request finished or whatever
UI'm trying to make it so my http interactions bot edits the message after initially acknowledging it
Uwas just typing that out haha
Uuhhh, I'm not sure how I'd do that with how my structure is rn
UI'm just doing it how I saw others do it lol
UUignore the insanely wrong usage of waitUntil
Uoh sorry I read this wrong
Udyslexia 
Uread it as waituntil after returning haha
Uwell I don't even need to do that haha
Ui should just need to do waitUntil(handleInteraction) i believe
Uconsidering the edit happens there :p
Uyeah lol its too long for a small snippet of code
Udidnt wanna flood too bad
Ualso isnt this incorrect syntax?
Ustill a bit unsure on waitUntil syntax but the typechecker yells at me for that :p
Uyeah
U:p