Can you do cronjobs in python by any chance? Or not yet
Can you do cronjobs in python by any chance? Or not yet
Clooks like no https://discord.com/channels/595317990191398933/1224715939581530112/1263968631453253664 they have a lot of other limitations rn with no packages anyway
.Oh yes that’s true, wouldn’t be able to install it anyway. Thanks again
Iwasm on workers is not there yet
let alone wasm on workers that ships as expensive of a runtime as python's
let alone wasm on workers that ships as expensive of a runtime as python's
CI don't think there's any big issue with wasm on workers as a whole, plenty of people use Rust workers and such
Most of the issue the team said was just in startup costs and such which they're working on, hopefully we'll see more of that soon
let alone wasm on workers that ships as expensive of a runtime as python'sThe Python runtime is embedded into the workerd/worker runtime (pyodide), so it's just your python code + packages and any overhead of pyodide/python.
Most of the issue the team said was just in startup costs and such which they're working on, hopefully we'll see more of that soon
GHi all, wondering if anyone has ever seen the error
ReferenceError: wasm_438b3227c4b242399e8c7376cf44cc39d16dcd3c is not defined when trying to develop a next.js app locally in wrangler devprisma@cloudflare/next-on-pages?GIt seems related to the prisma query engine, but I'm not exactly sure how to work around it
IThe Python runtime is embedded into the workerd/worker runtime (pyodide), so it's just your python code + packages and any overhead of pyodide/python.ah i did not know that.
i expected python to compile to wasm (including the runtime) and be executed by the wasm runtime.
rust->wasm for workers' boiler (iirc with axum) plate was massive
iirc 300k
iirc workers have a limit of 1M
ignoring actual useful payload that is way too large for comfort
IWorkers have a limit of 1MB only on the free plan. Paid is now 10MB 
Iah
GYeah, this is a blocking issue for me so I'll try and file a GitHub issue with more detail today 
.Does this include it being at an hour interval too? 15 mins cpu time
Cthe exact wording is this
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.https://developers.cloudflare.com/workers/platform/limits/
.So which one includes at an hour 
Cso I have no idea because those are both "less then" and "greater then" and not equal to
.Good old docs
Cyou fall into some magical space inbetween both where you get 7.5 minutes /s
Cyea idk, would just have to try and see
.Make a cron job be 1hr 1 min? 
GI figured it out!!! Upgrading to latest 
yarn- workspaces, and running
next devwith--turboresolved this issue (I was about to lose it) :SmileW:
SCloudflare has died at CN.
Duse durable object to implement yourself
Dor postgres, redis, etc
II just randomly ran into a cool open-source Segment Alternative Self Hosted On Cloudflare Workers https://evefan.com, I think they recently launched! Great work to the person who made this, will be watching closely!
GCloudflare Docs
Use the
connect() API to create outbound TCP connections from Workers.
Gthis is unanswered too :c
CI don't believe there has been anything official. But you can see the workerd runtime for code changes for it
Gdoesnt look good ig
Lthat table in the documentation is broken
IThanks - I mentioned this to the docs team.
IFixed now - thanks!
BHi everyone, it looks like the worker's metrics are wrong today. I have access to the dashboard and see the number of request for last 24h is different when i accesss to the detail.
Bfor example :
R@Chaika So I was wondering do you think I can see it again yet still?
--> https://discord.com/channels/595317990191398933/1270436774648221828/1270465952202494074
I'll return next week to ask again, Thank you.
--> https://discord.com/channels/595317990191398933/1270436774648221828/1270465952202494074
I'll return next week to ask again, Thank you.
ROr @andrew | as1003
A?pings
FPlease 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.
.When testing cron triggers using wrangler, are the same limits applied to them as if you weren't testing?
MDoes worker rate limiting prevent new workers being invoked or does their request trigger a worker to check if their limit is exceeded?
RThe latter
RYou are still billed for rate limited requests, assuming you are referring to the workers rate limiting API
Mthanks! Is this the same for setting up rate limits in WAF dashboard?
RNo, that one will actually prevent workers invocations
MIt says this in the docs “The Rate Limiting API is backed by the same infrastructure that serves the Rate limiting rules that are built into the Cloudflare Web Application Firewall (WAF).”
RThe underlying infrastructure might be the same, but the WAF rate limiter runs before a worker is invoked, unlike the workers rate limiting API