Dooh nice now all my builds are stuck in "queued" status
EIs there any way to group workers into nice folders or something
Daccording to the docs, there are unlimited build minutes for workers while it is in beta
NHi all, any idea why "nodejs_compat" is not showing in the flags list when trying to edit combability flags from the ui?
NLot of flags are showing, but not "nodejs_compat'".
VWait fir what? It’s already 3rd day. Is CF discontinuing the browser rendering product? Its channel is also archived.
L
L:COOLBEANS: i love workers
PWhy is there a difference for schedule expression in Cloudflare?
For example:
According to crontab.guru (https://crontab.guru/#0_3_*_*_1-5) this should run
But in Cloudflare dashboard it shows as
For example:
0 3 * * 1-5According to crontab.guru (https://crontab.guru/#0_3_*_*_1-5) this should run
At 03:00 on every day-of-week from Monday through Friday.But in Cloudflare dashboard it shows as
Schedule:At 03:00 AM, Sunday through Thursday and also executes like that.VThe browsers stopped working from 6th November. Neither we can start a browser, nor use an existing sessionId.
Mhm, maybe this was never fixed https://community.cloudflare.com/t/workers-cron-triggers-triggering-wrong-days/212893/5
AThat seems to be a bug. Did you create a ticket?
VI opened an issue on Comminuty as the Free plan customer can't create ticket.
https://community.cloudflare.com/t/unable-to-connect-to-any-of-the-browser-sessions/733818
https://community.cloudflare.com/t/unable-to-connect-to-any-of-the-browser-sessions/733818
Jwhen using workers RPC, how can I get the return type of a worker method?
Jin this case a durable object
Jhow do I get the type of mostRecentOrders without making a durable object stub?
JHmm, so it seems the problem is there some type difference somewhere inside date objects
AYou guys are making so many awesome things. Where do I even learn about cloudflare workers. All i see is examples.
FCloudflare Docs
Set up and deploy your first Worker with Wrangler, the Cloudflare Developer Platform CLI.
JI guess I just need to explicitly declare my return values..
Ea NAFS would be really great
VI am on a Worker paid plan, can't open a support ticket?
The support page ask to upgrade the website, but I don't need a website. Just worker paid is enough
The support page ask to upgrade the website, but I don't need a website. Just worker paid is enough
Ois deploying workers down for anyone?
CCorrect. You need a paid zone to be able to open tickets. Everyone is able open Account, billing and registrar tickets.
WWhat are you seeing?
SIf I am using Workers Websocket without Durable Objects (for example using it for listening to queues or as a proxy for another websocket server), how would the pricing work? Is it charged based on per request (hence per websocket connection) and the cpu-time used to process the websocket messages?
FBoth CPU time and per Worker request (not subrequests the worker does)
SMax of 30 seconds of CPU time per invocation - is this happening on the websocket ?
IYes. But keep in mind this is CPU time, not wall time (not time as measured on a clock but time that is measured based on how much compute you are doing)
II also believe a Websocket message resets that limit? (someone would have to confirm though)
FWebsockets seem to have indeed a very long or infinite timeout if I read this correctly -> https://community.cloudflare.com/t/how-can-i-use-a-worker-for-real-time-stuff-limits/325031/2?u=fry69
SOkay, I tested it, it stays longer than 30 seconds. a 2-minute connection was provided.
I30 seconds is cpu time.
ILet me see, I believe I had a tag for this.
I?cpu-time
FCPU Time: the amount of work the CPU needs to do, measured in
Wall Time: the actual amount of time a Worker runs for, as though you measured it with a clock or your browser DevTools
ms. More CPU-heavy things will increase it (for example, hashing passwords). This is not the same as the time a fetchWall Time: the actual amount of time a Worker runs for, as though you measured it with a clock or your browser DevTools
FUnless you have an endless for loop running in your worker to eat CPU time, you might have just measured real (wall) time, which does not matter. Workers can run for a year I think if they do not consume CPU, see -> https://developers.cloudflare.com/workers/platform/limits/#duration
IYou get 30 seconds of cpu time, so that means that if your WebSocket isn't doing much it could theoretically last for many minutes, although it's not a 100% because sometimes websockets are killed by Cloudflare for internal reasons.
S"wall time" is not included in the fee ?
Sand execution duration ?
FCorrect. Wall time does not matter, only CPU time.
For billing only CPU and number of Worker requests matter (not subrequests).
For billing only CPU and number of Worker requests matter (not subrequests).
Sthere is no pricing based on durable object logic, is there?
Sis there any link explaining?
FSI'm confused about this.
SCan this method be similar to the durable object pricing?
Sbecause 1 request fee is 1 hour connection and more
Sam I wrong?
1I kinda assumed that WebSockets on Workers would just get charged at the same rate as WebSockets on DOs, by GB-sec
Uwasnt sure where to post this so i assume this is where, but, is it possible to entirely limit access to a cloudflared tunnel to a worker?
