Queues maybe? You could limit consumer concurrency to a low number
Queues maybe? You could limit consumer concurrency to a low number
JAssuming you can batch them up into jobs or similar
JI don’t know of any easy way other than that, outside of using durable objects to track and throttle
Dah yep, sounds like queues would be the "easiest" using 
max_concurrency. Dmight be too much of a hassle for this project to rewrite it with queues in mind, but probably should refactor it to do that eventually
CYou can use the GraphQL API to get the metrics https://developers.cloudflare.com/analytics/graphql-api/tutorials/querying-workers-metrics/
<y'know I gotta say,
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: is the most obnoxious, frustrating type of error I've ever seen. This is so unhelpful to the point of making me want to flip a table.<The whole stack trace below just points to the miniflare lib, not my own code, so I have no idea what ever causes this, I have to fumble in the dark like a caveman using ECMAScript 1 in 1998
JCommon issue right now, sorry! There’s a fix up at https://github.com/cloudflare/workers-sdk/pull/4719 which should hopefully land soon
GitHub
Fixes #4715.
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
What this PR solves / how to test:
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you'd see an error like [ERR_ASSERTION]: The expre...
<I have an older version of the worker lib, so does it come from elsewhere?
<Can't wait for this to be fixed either way this is really aggravating and I don't like the feeling of frustration that comes with it
JHow old? This was introduced a couple months ago I think
<3.0.0 I think
JYou can grab the pre-release in that PR if you want to give it a try
<I rolled back after trying to update from a warning lol
<I'll try the PR, that might at least hold me off until the fix
J3.0.0 is very very old, I would definitely not recommend a version that old
<Tru dat
<Actual errors 
SThank you, I'll take a look at this
FHey, is cloudflareworkers.com an official Cloudflare domain/service?
CBest place for an official answer would be an account ticket with support. I don’t think there’s anything wrong with doing it given you have permission
Jfrom the early days, but yes - here is a release notes that references it: https://community.cloudflare.com/t/2018-11-29-workers-runtime-release-notes/47396
CSI gave this a shot. It's a bit complicated but from what I can see, the workers endpoint you referenced is specifically for workers. I found an endpoint for "pages", but i'm unable to get the name of the pages project in the results. I instead get back a randomized
Any insight on this? Are there any other solutions? I find it bizarre that I can't get a breakdown of usage per project (without going into 50+ project dashboards manually). Hopefully Cloudflare is working on some improvements to that.
scriptName e.g. pages-worker--123456-production for each invocation.Any insight on this? Are there any other solutions? I find it bizarre that I can't get a breakdown of usage per project (without going into 50+ project dashboards manually). Hopefully Cloudflare is working on some improvements to that.
KLook at the GraphQL calls that the individual project dashboards are making
KAll metrics in the dash are just GraphQL or API calls that you can make yourself
SGood idea
OSorry for the dumb question, is it possible to use
await cache.match() within a worker to pull a json file within a private R2 that I would otherwise access with the original await env.bucket.get() method? Wondering because it won't have a url to build the cacheKey
SSI've even got a PDO connector for D1 SQL
SHi, how do i get access to browser workers, currently getting the following error
workers.api.error.no_access_to_browser_worker [code: 10088]
workers.api.error.no_access_to_browser_worker [code: 10088]
CNo way to delete, all data is deleted after 93 days though, at which point the dataset will be gone too
EI'd probably email security@cloudflare.com for a request like that
EThough if you already have a support ticket that's fine too, we can take it from there
CYou can have custom role icons which is the cloud
CIt’s a server boosted perk. See https://support.discord.com/hc/en-us/articles/4409571023639-Custom-Role-Icons-FAQ
NHey, just curious if its possible to setup a Cloudflare Worker that only handles CORS policies and use that Worker in all the other Cloudflare Worker scripts that need CORS policy implementation? - I don't understand CORS fully so, if this is not possible just let me know, thank you
AIs there any way to know at execution time how much subrequests has done a worker? I'm reaching the limit and I'd like to know it to have unless one extra subrequest available to write in db the progress done at first attempt
Asorry, cat & keyboard
LHi, does anyone know how to get the r2 endpoint when running the worker locally? I need that for using pre-signed urls in local environment.
KLocal development doesn’t emulate the S3 API so there is no endpoint, you’d need to hit the production/live one
IThe subrequest limit should be documented based on the plan the Worker is on, if that's what you mean?
IAI saw the limits, the problem is the function i'm developing need more or less subrequests depending on different things... so it would be useful knowing when it's going to crash into a "Error: Too many subrequests" loophole
Aso I could stop the loop, save a bookmark in the database, and "paginate" the work
