just shared on github 😄

Account id= 71571c8606d2bb2c159c3a610b341bda
I think these are the namespace ids:
87bd98f1d14d44ccafc5f0d8d455165a
c9ef7bc233314704b08f8304750a628d

here again

ty, @Rob [KV, Queues] ^

Im not 100% sure if the issue is still going, but i havent gotten a 90% email yet

considering, i got the 50% email quite early compared to usual, im guessing its still an issue

usually comes at around 6pm, it was at 10am yesterday and about 10am today again

> Cloudflare is investigating reports that Workers KV write operations are being counted multiple times resulting in free tier overruns. > > We are working to analyse and mitigate this problem. More updates to follow shortly.

Thanks for the update. Keep me updated, if you need any additional information, feel free to ping me 😄

Hey everyone - have an open incident for this (see status page above).

The increased usage should not continue to accrue.

We're looking into how to reset any daily usage limits that have been overrun

Oki, thanks 👍

Thanks for reporting

noob question, is workers able to help with a problem like this? This website uses php7.0 on an AWS server and i have to work with it as it is.. T_T this wordpress revoluion slider and scripts are like gazillion versions behind, everything is working but this CPU/eval/parse times are ridiculous, how would you guys tackle this?

Please don't tag people for help, when someone knows how to answer your questions, they will

Ok sorry no prob

Does anyone know if V8 JIT optimzations are cached across isolates somehow, so a worker could benefit from them?

does anyone here have source code for sending emails in workers?

I believe that this currently does not exist. However, there are restrictions in what you can do during the startup of the worker such that they would be able to implement caching the initial state after the startup. AFAIK this is not yet being worked on (at least not in the public workerd repo), and I'm not sure how that would relate to JIT optimizations.

Hi all - noob question, I'm building an app for a third party customer to be deployed on cloudflare workers. It's currently running under my account and namespace whilst in dev and test. Once it's completed, what is the best way to handover ownership of the app to the customer, assuming they have no knowledge of cf workers?

use a config file to setup the ci cd

i have a question about worker invocation lifetime. is there any difference between these two approaches? 1.

try { return new Response('ok') } finally { await sendLog() }

2.

context.waitUntil(sendLog()); return new Response('ok')

Joined the waitlist for puppeteer ages ago. Has anybody got access? https://blog.cloudflare.com/introducing-workers-browser-rendering-api/

Or is there another way to run puppeteer on Cloudflare Workers?

The 1st probably will never finish the second promise

As soon as a Response is returned, that's the hint that the request lifecycle is over

waitUntil

is what tells it to stay up

I mean that's a general JS thing with a

return