in the docs it says the package i want is supported
in the docs it says the package i want is supported
IThe docs are misleading and I'm working to get them clarified - there are no supported packages built-in currently.
Toh my gosh lol.. ive been at this for hours because the docs said the particular list was supported packages 
Ttrying to figure out what in the heck im doing wrong
TCloudflare Docs
To import a Python package, add the package name to the requirements.txt file within the same directory as your wrangler.toml configuration file.
Tright here on the built in packages list
Tso what is and is not supported here ?
INothing except the stdlib I believe: https://developers.cloudflare.com/workers/languages/python/stdlib/
Toh I think Im seeing now, this is the doc for the future release of the support of requirements ?
IYes, exactly.
Tah crap ok
TI understand, it was also a bit of a misunderstanding on my end skipping over the part that the requirements files are not yet implemented
II'm trying to follow up to get that warning made more visible or the page updated for this exact reason - it can cause confusion.
Tits ok, i like workers and using CF so far, previously I've been deploying stuff ith vercel and render, I believe CF with like a remix stack and just using everything in house for the tools / cost balance is almost a no brainer its so good
Tobviously some limitations on the workers and excitement on my end to see them expand more and get more features
Eyou can probably do
*/* or *mydomain.com/* ?
Oso i know that d1 is the native database for cloudflare, but due to it missing features such as read replicas which are pretty important, does it make sense to use hosted turso instead with its replicas and libsql?
NIs there a way to force workers to run in specific zones?
HA Worker will only run on zones it is bound to, if that is what you mean?
Cdo you mean zone as in cloudflare zone/website or zone as in some sort of geographical region
NYeah it is currently trying to find the closest to the user
NGeographical
CThere's smart placement: https://developers.cloudflare.com/workers/configuration/smart-placement/
If you need it for legal reasons or some very strict "only ever in x country/region" there's Enterprise's Data Localization suite stuff
If you need it for legal reasons or some very strict "only ever in x country/region" there's Enterprise's Data Localization suite stuff
Cloudflare Docs
Speed up your Worker application by automatically placing your workloads in an optimal location that minimizes latency.
NI know smart can place it closer to one of its region of other services like database but it doesn't do that for other APIs
NId prefer to min max the latency between the api and the worker rather than the latency between the worker and the user
Chmm what do you mean for "other APIs"? It does it with fetch requests from your worker
Smart Placement is enabled on a per-Worker basis. Once enabled, fetch requests (also known as subrequests) from your Worker are analyzed regularly. The Smart Placement algorithm determines the optimal placement to minimize the round-trip time (RTT) between the Worker and the back-end service the Worker is communicating with.https://developers.cloudflare.com/workers/configuration/smart-placement/
Smart Placement is only active for Workers that make more than one roundtrip to back-end infrastructure. If your Worker does less than one subrequest on average, Smart Placement will run the Worker at the data center closest to the user.
Smart Placement is a best-effort attempt. Smart Placement will not take action unless it is more performant than the default (which is running the Worker at the data center closest to the user).
Smart Placement only affects the execution of fetch event handlers. Workers without a fetch event handler will be ignored by Smart Placement. For Workers with both fetch and non-fetch event handlers, Smart Placement will only affect the execution of the fetch event handler.
NHow does it determine that it does have to move, here is says that it has to do a minimum of 1 subrequest but does it have to be the exact same?
NBut i believe i shouldnt worry since smart placement will figure out if it really is worth it or not
NThanks a bunch
Iguys
was there an outage for cron triggers for a few hours today from ~8:30am to ~3:30pm US Eastern Time?
i get stats sent to me every 30mins using workers cron triggers that i check whenever i find time in the day but the stats for ~8:30am to ~3:30pm seem to be simply missing.
was there an outage for cron triggers for a few hours today from ~8:30am to ~3:30pm US Eastern Time?
i get stats sent to me every 30mins using workers cron triggers that i check whenever i find time in the day but the stats for ~8:30am to ~3:30pm seem to be simply missing.
Cshould be same origin/per ip afaik, and yea it'll see if it's more performant to move or not
Cnothing in #cloudflare-status , I have ~8 or so crons running once a minute which seem fine but could be more specific. I would check your Workers Logs -> Cron Events to see if it ran or not
Iuh this is supposed to not be empty, right?
Cuhhh looks unrelatedly broken
Wugh
W
Wand event logs is the same
Wsigh
Cshould I escalate or you got it?
Wpls
Cwell that's raised but yea as far as I know/people have reported (and lots of us champs use cron events & notice stuff pretty quickly) cron events seem fine, maybe an issue with your worker?
Iwith just my worker?
i havent touched it in months tho
i havent touched it in months tho
CI assume it relies on some external components to work.
When cron events are fixed you'd be able to see if it executed or not, although errors details/logs
When cron events are fixed you'd be able to see if it executed or not, although errors details/logs
D
Cshould be fixed now, can look back at those cron events, should be able to look back that far I think if you've only got it once per 30 mins
Iall of them are success
however the stats were simply not sent to me for those few hours
very weird
ive been using workers for years and this is the first time this is happening
maybe im assuming this is workers fault
maybe my infra thats supposed to "receive" the stats were down
however the stats were simply not sent to me for those few hours
very weird
ive been using workers for years and this is the first time this is happening
maybe im assuming this is workers fault
maybe my infra thats supposed to "receive" the stats were down