so do fines 🙂

If you get fined for down time maybe consider never deploying code so ur never down 😛

guess thats why we have staging lol

except for last night, where V8 decided to change how dates are printed at runtime lol

well I mean locale data changes so you cant really always expect a locale to print a certain way

so we should stop deploying if we want it to come back, catch up?

All of the undeployed deployments are in a queue - happening in the order they came in at

You're welcome to make additional ones, it'll just go to the end of the queue

any rough eta, so we can let other teams know

The public info is in the status page

what was odd for us and is still happening, after a deploy at 6pm, the worker has something to check the req pathname and then basically set that pathname in a cookie. For some reason, the request for our main.js was being picked up in the worker as the req pathname and being set client side. The actual worker code wasnt changed, but only the KV assets. Im guessing it couldnt find the main.js or something because the manifest in the worker didnt tie up to the hashed main.js Something like that. Is there no way to tell when a specific worker has caught up with deploys?

you can add headers with a version you know and you will know when it updated

no

service environment versions plsssssss

message has been deleted

hi 👋 regarding supported algorithms in workers' web crypto impl (https://developers.cloudflare.com/workers/runtime-apis/web-crypto/#supported-algorithms), is there any chance of RSASSA PKCS1 v1.5 being supported for encrypt/decrypt? currently it's just for generate/import/export

if not, any ideas for a workaround?

Use RSA-OAEP. https://github.com/diafygi/webcrypto-examples#rsa-oaep---encrypt

unfortunately we need specifically this algorithm for compatibility w/ a legacy client; we're aware of the security issues but don't have a choice here

check if pkijs has it. https://pkijs.org/

Oh, so Worker deploys are broken too?

this looks great, thank you

lemme know if it works, if not I have other ideas to point you towards

would be cool to ping workers status prior to deployment, and if there is any issues, warn before deploying

just saying

Is there any that work for openapi?

https://github.com/cloudflare/itty-router-openapi is neat

yeah that's what I usually use

oh https://github.com/anatine/zod-plugins/tree/main/packages/zod-openapi and https://github.com/asteasolutions/zod-to-openapi

is anyone aware of any progress on the browser rendering API? did the waitlist a few days ago and wondering if anyone non cf-employed has access yet