``` Concurrent Subrequest Limit As of this release, we impose a limit on the number of outgoing HTT

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

Concurrent Subrequest Limit

As of this release, we impose a limit on the number of outgoing HTTP requests that a worker can make simultaneously. For each incoming request, a worker can make up to 6 concurrent outgoing fetch() requests.

This means that something like this:

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

await Promise.all(jobs.map(async (job_url) => await $fetch(job_url))

Would take very long right?
It would do 6 + 6 + 6 + 6 until it reaches the limit of 50 per request

Jonah•4/12/24, 10:20 PM

Does

*domain.com/*

*domain.com/*

in a Cloudflare worker trigger, no longer process all requests? A few months ago, that trigger pattern ran on every request, domain.com/style.css and so on, now it only runs on / ?

Ccosbgn ``` Concurrent Subrequest Limit As of this release, we impose a limit on the nu...

kian•4/12/24, 10:27 PM

Not quite 6+6+6+6

kian•4/12/24, 10:27 PM

Once one finishes, another one can start

kian•4/12/24, 10:27 PM

It's just 6 concurrent, not batches of 6

Ccosbgn ``` Concurrent Subrequest Limit As of this release, we impose a limit on the nu...

bun•4/13/24, 12:32 AM

https://flareutils.pages.dev/promisequeue/ there's an util developed for this specific usecase. runs 6 promises concurrently

PromiseQueue | Flareutils

Small Utilities and little goodies that make developing with Cloudflare easier and faster.

dom•4/13/24, 7:58 AM

Workers wrangler logs and realtime logs are not returning anything for a specified worker. Is anyone else experiencing these issues?

DeChill•4/13/24, 4:19 PM

Hi, is there any way to trigger workers in response to Messages from an external Kafka topic?

oof2win2•4/13/24, 4:58 PM

i dont know if im going insane at this point, but i have this weird scenario. i have a public api and a discord bot that both have the same functionality essentially, so i was thinking that i would take out the core api functionality, put it into a separate worker and make the api and discord bot have bindings to the core functions

oof2win2•4/13/24, 4:59 PM

does this make sense? like the main benefit would be that the discord bot wouldnt be using http calls to communicate with the worker

Ooof2win2 does this make sense? like the main benefit would be that the discord bot wouldn...

Beny•4/13/24, 5:00 PM

Yes that would be good, no point having 2 copies of the same code

oof2win2•4/13/24, 5:01 PM

hmm ill think it over

oof2win2•4/13/24, 5:01 PM

might be weird with auth and file uploads

oof2win2•4/13/24, 5:01 PM

thanks though, at least im not going insane

onnimonni•4/13/24, 7:16 PM

Has someone created tests for scheduled workers with correct typing?

I'm trying to create a test for my scheduled worker and the default typing for a scheduled worker seems to work like this:

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

async scheduled(event: ScheduledEvent, env: Env, ctx: ExecutionContext): Promise<void> {
        console.log('This is a scheduled event');
    },

When I want to call this

scheluded

scheluded

in my test I did this:

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

it("scheduled event logs 'This is a scheduled event'", async () => {
            const controller = createScheduledController({
                scheduledTime: new Date(1000),
                cron: "30 * * * *",
            });
            const ctx = createExecutionContext();
            await worker.scheduled(controller, env, ctx);
            await waitOnExecutionContext(ctx);
            expect(ctx.log).toMatchInlineSnapshot(`"This is a scheduled event"`);
        });

The typing seems to want an

ScheduledEvent

ScheduledEvent

but I didn't find anyway to mock those. The only related mocking function seems to be

createScheduledController

createScheduledController

but it's type is

 ScheduledController

 ScheduledController

which is similiar but not the same.

onnimonni•4/13/24, 7:17 PM

Second question is that can I somehow test the side effects of the function like what it logs?

The scheduled functions don't return anything so testing the return values is impossible

onnimonni•4/13/24, 7:24 PM

Well I was able to fix this by allowing either

ScheduledController

ScheduledController

ScheduledEvent

ScheduledEvent

typing in the scheduled event and by following this stackoverflow answer on testing the logging: https://stackoverflow.com/questions/76042978/in-vitest-how-do-i-assert-that-a-console-log-happened

Stack Overflow

In Vitest, how do I assert that a console.log() happened?

The question's in the title. With Jest it was console.log = jest.fn(). How do I get and analyse the console output of the code I'm testing?

Kkian await scheduler.wait(ms)

Shravan•4/13/24, 11:21 PM

is there any difference between scheduler.wait and

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

export const sleep = (ms: number): Promise<void> => {
    return new Promise<void>((resolve) => setTimeout(resolve, ms));
};

and how they work in workers?

SShravan is there any difference between scheduler.wait and `export const sleep = (ms: n...

Beny•4/14/24, 12:23 AM

I think it fixes Date.now() if I remember correctly

BBeny I think it fixes Date.now() if I remember correctly

Shravan•4/14/24, 1:29 AM

you mean if we use date.now after scheduler.wait?

Unsmart•4/14/24, 1:34 AM

Its just an awaitable alternative of setTimeout. So its basically exactly the same.

Armaan from Armenia•4/14/24, 6:54 AM

how do I get rid of this for the dev to challenge?

Armaan from Armenia•4/14/24, 6:54 AM

deadline is 6 minutes away and I used it all

Armaan from Armenia•4/14/24, 6:54 AM

help

AArmaan from Armenia how do I get rid of this for the dev to challenge?

onnimonni•4/14/24, 9:01 AM

Read the error. You have already used your free quota. Sign up for the paid workers plan for 5$. You can stop using it when you don't need it anymore.

Oonnimonni Read the error. You have already used your free quota. Sign up for the paid work...

Armaan from Armenia•4/14/24, 9:20 AM

Thank you so much! Updated!:D

Migmac•4/14/24, 12:50 PM

Where can I submit a feature-request / extension / suggestion?

Erisa•4/14/24, 12:51 PM

#workers-feature-suggestions

Migmac•4/14/24, 12:51 PM

Thank yoU!

neoney•4/14/24, 8:28 PM

Worker supposed to run every minute on cron

all recent triggers have been erroring, trying to debug, does not seem to be running anymore

neoney•4/14/24, 8:29 PM

ive been tailing for 6 minutes

neoney•4/14/24, 8:29 PM

no logs

neoney•4/14/24, 8:30 PM

does tail not show logs from cron?

Walshy•4/14/24, 8:38 PM

tail does show

Walshy•4/14/24, 8:39 PM

Are you on a paid plan?

Walshy•4/14/24, 8:39 PM

you're averaging a lot of cpu time per execution

WWalshy Are you on a paid plan?

neoney•4/14/24, 8:47 PM

yes

WWalshy you're averaging a lot of cpu time per execution

neoney•4/14/24, 8:47 PM

yeah its a worker that goes through all database stuff that hasnt been processed and sends webhooks

neoney•4/14/24, 8:47 PM

ive added a try catch over the main functions

neoney•4/14/24, 8:47 PM

and deployed it

neoney•4/14/24, 8:47 PM

suddenly its green, and i have logs

neoney•4/14/24, 8:48 PM

and no logs errored

neoney•4/14/24, 8:48 PM

:thinkRoll:

Walshy•4/14/24, 8:48 PM

yeah tail should be fine, i can check one of my workers real quick

neoney•4/14/24, 8:48 PM

no clue what that was about.

neoney•4/14/24, 8:48 PM

tail working now

neoney•4/14/24, 8:48 PM

the worker wasnt working for like a day i think

neoney•4/14/24, 8:48 PM

ended up with

  (warn) Log size limit exceeded: More than 128KB of data (across console.log statements, exception, request metadata and headers) was logged during a single request. Subsequent data for this request will not be recorded in logs, appear when tailing this Worker's logs, or in Tail Workers.

  (warn) Log size limit exceeded: More than 128KB of data (across console.log statements, exception, request metadata and headers) was logged during a single request. Subsequent data for this request will not be recorded in logs, appear when tailing this Worker's logs, or in Tail Workers.

because it did so much at once lol

Walshy•4/14/24, 8:49 PM

haha

neoney•4/14/24, 8:52 PM

actually something's still wrong with it

neoney•4/14/24, 8:52 PM

but the code might be wrong

``` Concurrent Subrequest Limit As of this release, we impose a limit on the number of outgoing HTT

Similar Threads

Similar Threads

Similar Threads