waitUntil is wall-time iirc

K

kianOP•9/13/24, 7:23 AM

Yeah, it's wall-time.

Kkian waitUntil is wall-time iirc

H

Hello, I’m Allie!•9/13/24, 7:23 AM

Wait wut

H

Hello, I’m Allie!•9/13/24, 7:23 AM

Rlly

H

Hello, I’m Allie!•9/13/24, 7:23 AM

Ughhhh

K

kindaraffy•9/13/24, 6:02 PM

Did anyone manage to get the sentry integration going (setting up sentry init) using Worker RPC (WorkerEntrypoints)? The docs only mention how to use sentry when you are using a handler (like fetch), but im not sure how this can be done with workers that only expose a WorkerEntrypoint.

https://docs.sentry.io/platforms/javascript/guides/cloudflare/#setup-cloudflare-workers

Cloudflare | Sentry for Cloudflare

Official Sentry SDK for Cloudflare Workers and Cloudflare Pages.

M

Mozzy•9/13/24, 7:11 PM

Possibly a dumb question. What is the best way to fetch my Worker from that same worker? Is it literally just fetch()ing the remote endpoint or is there a smarter way?

Oom Use RPC or service binding

M

Mozzy•9/13/24, 8:14 PM

Are there any good examples of this?

M

Mozzy•9/13/24, 8:18 PM

Thanks

A

achesui•9/13/24, 9:06 PM

does anyone has used cloudflare workers with twilio for calls?, is it a good idea?, cloudflare is not clear when talking about websockets pricing..

S

sadel•9/13/24, 9:51 PM

is there a way to have multiple .dev.vars files for each env (eg, prod, staging) and maybe programmatically inject, similar to using dotenv and .env files?

M

MarcusAurelius•9/14/24, 4:30 AM

Has anyone got ytdl-core or @distube/ytdl-core working on cloudflare workers after release of nodejs_compat_v2 ?

Jjlworkshop Hello everyone, when I deploy my worker, it always enable the workers.dev sub do...

D

DaniFoldi•9/14/24, 7:28 AM

Hey, could it be because you put

workers_dev = false

workers_dev = false

workers_dev = false

workers_dev = false below a table? In toml, everything below [some table] is part of that table. You can try moving it to the top, or sharing your config so we can take a look - all the id’s are safe to share, makre sure you don’t have anything sensitive in environment variables (use secrets for that)

Bblank I'm seeing my workers on free plan show `2010ms` as the CPU time before being ki...

A

Ashley•9/14/24, 12:50 PM

I’m pretty sure that while the WS connection is open, the Worker is also going to keep running. That’s why Durable Objects are recommended for WebSockets, as they can hibernate when not handling messages: https://developers.cloudflare.com/durable-objects/reference/websockets/ (Workers Paid required)

Cloudflare Docs

Durable Objects with WebSockets | Cloudflare Durable Objects docs

WebSockets allow real time communication between a client and server. Both Cloudflare Durable Objects and Workers can act as WebSocket endpoints – either as a client or as a server.

A

Ashley•9/14/24, 1:13 PM

Ah, yeah, probably - it’s not a “hard cut off” in my experience - I’ve seen it with cron triggers that run more regularly than an hour and they can be a bit hit-and-miss with keeping to the hard limit

Bblank yep it's expected it will stay running. I'm just trying to calculate the maximum...

C

Chaika•9/14/24, 3:03 PM

There's a good explaination of how the cpu limits work here: How are CPU limits enforced in the free tier?

C

Craig•9/14/24, 4:22 PM

I have a DNS record that will not verify in my high level account, they said it was a cloud fare issue

Screenshot_12-9-2024_15566_app.gohighlevel.com.jpeg

C

Craig•9/14/24, 4:26 PM

its causing my emails not to get delivered

Original message was deleted

C

Craig•9/14/24, 4:28 PM

Its causing my emails not to get delivered, I know it says optional but still need a dmark record for it to work

C

Craig•9/14/24, 4:29 PM

not sure why my emails are not being delivered

C

Craig•9/14/24, 4:30 PM

thats just what Nexcess and high level told me, they said to contact cloud fare to fix this issue

CCraig I have a DNS record that will not verify in my high level account, they said it ...

I

Idle•9/14/24, 5:24 PM

seems like your dmarc record isn't propagating for some reason

I

Idle•9/14/24, 5:27 PM

but as leo said, this isn't whats causing your emails to not be delivered

I

Idle•9/14/24, 5:27 PM

p=none makes your dmarc record basically useless

M

Mr. Technician•9/14/24, 6:12 PM

I'm noticing that whenever my code has an error (say a call to function that does not exist) it won't throw an error, it will just hang indefinitely

M

Mr. Technician•9/14/24, 6:12 PM

the debugging process is very annoying because of it

J

James•9/14/24, 8:08 PM

Can you share a minimal example of that? Errors should absolutely be thrown. I'd suspect you might have something wrapping your code in a

try{}

try{}

try{}

try{} handler or something and not handling the errors?

M

Mr. Technician•9/14/24, 9:02 PM

I'll work on a minimal sample if i see it again

M

Mr. Technician•9/14/24, 9:02 PM

I have no try handlers implemented yet

M

Mr. Technician•9/14/24, 9:05 PM

the only thing I can think of is that I am using websockets and my code is in an async method that is not awaited

M

Mr. Technician•9/14/24, 9:16 PM

in short:

trips.get('/', async (c) => {  

    const upgradeHeader = c.req.header('Upgrade');
    if (!upgradeHeader || upgradeHeader !== 'websocket') {
        return new Response('Expected Upgrade: websocket', { status: 426 });
    }

    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);

    server.accept();
    server.addEventListener('message', event => {
        console.log(event.data);
    });

    run(); //issues occur in this function

    return new Response(null, {
        status: 101,
        webSocket: client,
    });
});

trips.get('/', async (c) => {  

    const upgradeHeader = c.req.header('Upgrade');
    if (!upgradeHeader || upgradeHeader !== 'websocket') {
        return new Response('Expected Upgrade: websocket', { status: 426 });
    }

    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);

    server.accept();
    server.addEventListener('message', event => {
        console.log(event.data);
    });

    run(); //issues occur in this function

    return new Response(null, {
        status: 101,
        webSocket: client,
    });
});

trips.get('/', async (c) => {  

    const upgradeHeader = c.req.header('Upgrade');
    if (!upgradeHeader || upgradeHeader !== 'websocket') {
        return new Response('Expected Upgrade: websocket', { status: 426 });
    }

    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);

    server.accept();
    server.addEventListener('message', event => {
        console.log(event.data);
    });

    run(); //issues occur in this function

    return new Response(null, {
        status: 101,
        webSocket: client,
    });
});

trips.get('/', async (c) => {  

    const upgradeHeader = c.req.header('Upgrade');
    if (!upgradeHeader || upgradeHeader !== 'websocket') {
        return new Response('Expected Upgrade: websocket', { status: 426 });
    }

    const webSocketPair = new WebSocketPair();
    const [client, server] = Object.values(webSocketPair);

    server.accept();
    server.addEventListener('message', event => {
        console.log(event.data);
    });

    run(); //issues occur in this function

    return new Response(null, {
        status: 101,
        webSocket: client,
    });
});

M

Mr. Technician•9/14/24, 9:34 PM

@James I think that is the issue. it's the call to run without awaiting it, which I need to do so I can open the websockets connection

M

Mr. Technician•9/14/24, 9:37 PM

boom, this fixes it

(async () => {
        try {
            await run(trip, engineConfig); //the method will return 101, but run() will continue
        } catch (err) {
            console.error('Error in run function:', err);
        }
    })();

(async () => {
        try {
            await run(trip, engineConfig); //the method will return 101, but run() will continue
        } catch (err) {
            console.error('Error in run function:', err);
        }
    })();

(async () => {
        try {
            await run(trip, engineConfig); //the method will return 101, but run() will continue
        } catch (err) {
            console.error('Error in run function:', err);
        }
    })();

(async () => {
        try {
            await run(trip, engineConfig); //the method will return 101, but run() will continue
        } catch (err) {
            console.error('Error in run function:', err);
        }
    })();

L

Limit•9/15/24, 12:22 AM

hey, i have a worker that works like this:

POST example-host.com
1st request: { "name": "bob" }
2nd request: { "name": "john" }
3rd request: { "name": "bob" }
etc.. (it alternates basically)

my problem right now is when im on cloudflare dns, the responses are correct, but any other dns resolver it seems to be caching the response even with cache-control, so i will be getting the 1st response no matter how many times i send the request

A

Avi•9/15/24, 2:34 AM

does deleting a tail worker require restarting the main worker?

W

Walshy•9/15/24, 2:59 AM

What do you mean restarting?

WWalshy What do you mean restarting?

A

Avi•9/15/24, 6:02 AM

sorry, that was super vague. the main worker is a DurableObjects, so I was wondering if that'd force a restart of the DO instance

A

akashra•9/16/24, 1:11 AM

Hah, I was just looking at writing some request data to files to re-use as tests/mocks, and found this in the docs:

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Starting on September 23rd, 2024, when your compatibility date is on or after 2024-09-23, the nodejs_compat compatibility flag will enable the exact same behavior as nodejs_compat_v2.

Had to double-take on the date: "We're in the future!"

D

DaCubeKing•9/16/24, 4:35 AM

Windows Smartscreen appears to be blocking the console/debugger when you attempt to edit a worker on the web!

Similar Threads

Similar Threads

Similar Threads