What plan are you on and what usage model is the Worker using?
What plan are you on and what usage model is the Worker using?
CThis is weird to me as your aren't returning a content-length header
JIt is working now. I made a few changes
JThank you for the help!
AI’m on the Workers Paid plan, and changed to Standard Pricing
AI checked the wall clock time out of curiosity (I know it’s not billed using that etc) and it was 7 or so seconds, so it’s not running for a particularly long time either and most is waiting on I/O
AThere's some interesting stuff in https://developers.cloudflare.com/workers/platform/limits/#worker-limits but it only talks about bundled vs unbound, and nothing about standard - with bundled having a 50ms CPU limit, which would perhaps explain it, but odd it doesn't talk about standard pricing and how that's handled (further down there's another note about unbound relating to CPU)
RI am still unable to secure my workers and pages; it seems the api tokens are either all or nothing in terms of wrangler usage. I anyone running into this problem? I think it's really important to have the API tokens such that they can be locked down to one particular pages or workers project for either production or preview. It feels like this is not a use case anyone is running into.
ZYup, you're not the only one. That's unfortunately not possible at the moment.
Msince the documentation is 3 years old and things may have changed, whats the general best practice for managing multiple cloudflare workers in a single repo? docs say use Lerna but figured Id double check here before diving down that road
EI've been hunting around for IMAP/POP client libraries that work on CF workers, however so far nothing has worked, not even with node compat. Is there anyone here with a similar need, maybe even building a lib themselves?
So far it seems like I have to write my own lib, and with the complexity and goofiness of the standards I'd rather not
So far it seems like I have to write my own lib, and with the complexity and goofiness of the standards I'd rather not
Mseems like lerna will work well but the docs suggest using
lerna bootstrap , Im not sure the intentions of that command for the purposes of cloudflare workers, but sounds like that command was deprecated and ultimately removed a while ago in favor of just regular "npm install"
Fpartykit
LHi yall, I just
inited wrangler project, and I am getting this non stop on wrangler devI had this happen before, but it eventually got fixed
LHappening again..
Laight restarting my mac fixed it? lmao
CDoes anyone have any idea of how much workers for platforms cost and what kind of limits they have?
H- Pricing: Contact Sales
- Limits
CThanks!
MIll take a peek. I added Lerna and that seemed to work fine for our use case, but Im interested to solve the cross-worker dependencies since I think the docs are outdated for that. if I come across solutions maybe Ill open a pr or something
KYou'd have to deploy the Worker everytime, but that's probably the best way to do it anyways.
KFetching R2/KV everytime vs updating the Worker once a week
KThat's still a deployment
KYou can use it though, yeah.
KWhat’s the issue with doing a deployment though?
KIf it's small enough to fit into your Worker without any issues, including it in the deployment is faster & cheaper
KWell, if you need it on every request.
JCan I do something like this using itty-router in Workers?
KJOh thank you
JThats what I was looking for
DUsing a non-R2 S3 API is oddly easier to cache, since you just have to use cacheEverything: true on the fetch.
DI use Backblaze B2 (with the S3 API) for some Workers that use caching heavily.
DHello there,
So I am using the workers to merge images together which takes about 1ms and then to upload it to the R2 storage (with the put command) which (at least wall time) takes about 500ms.
My app may make 5, 10 or 100 post requests without waiting for the previous one to finish and that's fine by me because it takes a lot of time to upload the image to R2.
The issue is, because of that, after just 5 or 10 requests I start to get 'service temporarily unavailable.'. Am I supposed to wait for the worker to finish, can I not make concurrent requests?
So I am using the workers to merge images together which takes about 1ms and then to upload it to the R2 storage (with the put command) which (at least wall time) takes about 500ms.
My app may make 5, 10 or 100 post requests without waiting for the previous one to finish and that's fine by me because it takes a lot of time to upload the image to R2.
The issue is, because of that, after just 5 or 10 requests I start to get 'service temporarily unavailable.'. Am I supposed to wait for the worker to finish, can I not make concurrent requests?
Dps: please tag me on the reply
AYou can check if they were caught by the rate limit from the Events section in Security on the Cloudflare Dashboard. I believe it’s 1,000 requests per minute
DI headed over to my website and then security and analytics and this is what I see
D
