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

C

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

its causing my emails not to get delivered

Original message was deleted

C

CraigOP•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

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

not sure why my emails are not being delivered

C

CraigOP•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!

DDaCubeKing Windows Smartscreen appears to be blocking the console/debugger when you attempt...

C

Cyb3r-Jak3•9/16/24, 4:53 AM

Unfortunately that happens from time to time. Best thing to do is report as safe and wait for Microsoft to unmark it as unsafe

B

Brett Willis•9/16/24, 5:22 AM

As we know, for better or worse workers run in front of the CDN cache, but we do have the Cache API available within workers. So all requests will still hit the worker, but we can at least reduce load/cost on our database by checking the Cache API first.
However, assets cached via the Workers Cache API cannot be purged globally (local data centre only). This can only be done with cache tags available on an enterprise plan (https://developers.cloudflare.com/workers/reference/how-the-cache-works/#purge-assets-stored-with-the-cache-api).
So it is impossible to implement coordinated caching and invalidation with the Workers platform except for customers on a several hundred thousand $/yr enterprise plan. Is this intentional? And will it change?

Cloudflare Docs

How the Cache works | Cloudflare Workers docs

How Workers interacts with the Cloudflare cache.

BBrett Willis As we know, for better or worse workers run in front of the CDN cache, but we do...

C

Cyb3r-Jak3•9/16/24, 5:23 AM

You can purge with the purge everything from that page

All assets on a zone can be purged by using the Purge Everything cache operation. This purge will remove all assets associated with a Cloudflare zone from cache in all data centers regardless of the method set.

C

Cyb3r-Jak3•9/16/24, 5:24 AM

and

To purge an asset globally, you must use the standard cache purge options. Based on cache API implementation, not all cache purge endpoints function for purging assets stored by the Cache API.

https://developers.cloudflare.com/cache/how-to/purge-cache/

CCyb3r-Jak3 You can purge with the purge everything from that page > All assets on a zone ca...

B

Brett Willis•9/16/24, 5:30 AM

Yeah but blasting away the entire zone any time a single asset changes is hardly efficient caching.
From how I read it, the only "standard purge endpoint" that functions is "purge by cache tag" which is an enterprise feature.

M

Marius B.•9/16/24, 7:40 AM

Hello! Does Cloudflare Snippets support the Cache API or Bindings?

0

0x146231489231923•9/16/24, 10:02 AM

hey everyone

0

0x146231489231923•9/16/24, 11:42 AM

love to discuss anything about cloudflare workers with you all

MMarius B.Hello! Does Cloudflare Snippets support the Cache API or Bindings?

W

Walshy•9/16/24, 12:42 PM

cache api yes, bindings no

0

0x146231489231923•9/16/24, 1:55 PM

is there

solved

solved

solved

solved status for question in #workers-help ?

M

Mr. Goodman•9/16/24, 3:30 PM

Hello

0

0x146231489231923•9/16/24, 5:32 PM

hello!

ℭ

ℭ𝔦𝔭𝔥𝔢𝔯•9/16/24, 5:38 PM

May I learn more about the benefits of using "workers for platforms" as opposed to the free variant please

ℭℭ𝔦𝔭𝔥𝔢𝔯 May I learn more about the benefits of using "workers for platforms" as opposed ...

A

Ashley•9/16/24, 6:17 PM

Workers for Platforms is designed to let you run your Customers’ code yourself, so it’s got nothing to do with free vs paid plans etc. - so you could allow customers to give you code, and then your Workers can execute their code. If you just want to build/deploy your own applications/websites, you don’t need Workers for Platforms

AAshley Workers for Platforms is designed to let you run your Customers’ code yourself, ...

ℭ

ℭ𝔦𝔭𝔥𝔢𝔯•9/16/24, 6:23 PM

perfect, thats very clear thank you

JJose Ramos My structure looks like this src/index.js src/router/routes.js index.js addEve...

K

Kevin•9/16/24, 9:31 PM

Hey @Jose Ramos - not sure if someone responded to you in time, but if you're losing the latest itty-router, we deprecated router.handle (in favor of router.fetch) earlier this year.

You can literally just replace the two in your code and that will work... however, you should check out the docs on https://itty.dev/itty-router/getting-started... your whole index.js file sounds like it doesn't need to exist

Basically you can just export an object that looks like

{ fetch: Function }

{ fetch: Function }

{ fetch: Function }

{ fetch: Function } (which is what itty-router now looks like), and be done. No need for this bit at all:

addEventListener('fetch', (event) => {
  event.respondWith(router.handle(event.request))
});

addEventListener('fetch', (event) => {
  event.respondWith(router.handle(event.request))
});

addEventListener('fetch', (event) => {
  event.respondWith(router.handle(event.request))
});

addEventListener('fetch', (event) => {
  event.respondWith(router.handle(event.request))
});

N

num•9/17/24, 6:18 AM

does anyone know if CF said anything about adding support for compressing assets in pages/workers using zstd similar to how they already do it with brotli and gzip? I've only found some community posts with google

Nnum does anyone know if CF said anything about adding support for compressing assets...

A

arch•9/17/24, 1:03 PM

https://discord.com/channels/595317990191398933/1040420029080018945/1285546053076127744

Aarch https://discord.com/channels/595317990191398933/1040420029080018945/128554605307...

N

num•9/17/24, 1:03 PM

omg thank you :clerhugged:

M

marko.333•9/17/24, 3:54 PM

What type of validation (if any) is done against the parameters of an RPC call (on the sending and receiving side)?

Mmarko.333 What type of validation (if any) is done against the parameters of an RPC call (...

H

Hard@Work•9/17/24, 3:56 PM

That it is serializable(and under the limit to be sent)?

H

Hard@Work•9/17/24, 3:56 PM

I don't think there is anything else

HHard@Work I don't think there is anything else

M

marko.333•9/17/24, 5:21 PM

OK, thx.

S

SC8•9/17/24, 6:50 PM

.toml [[vars]] and [vars] - Help me understand?

I just lost a bunch of time trying to debug vars not being available. Eventually I found [[vars]] was wrong, and [vars] is right, but many other items are [[ ]] format. Can anyone help me understand the when and why of [[ ]] vs [] so I don't make this msitake again? Thx.

S

SC8•9/17/24, 7:15 PM

very helpful - thank you Leo

SSC8 .toml [[vars]] and [vars] - Help me understand? I just lost a bunch of time try...

S

SC8•9/17/24, 7:23 PM

For others reference:

[] = Table -> https://toml.io/en/v1.0.0#table
[[]] = Table Array -> https://toml.io/en/v1.0.0#array-of-tables

It's great to keep on learning!

A

Ashley•9/17/24, 7:30 PM

And I learnt the hard way, don't put top-level key/value pairs (e.g. ones not in tables) below the tables... or they get ignored, many hours wasted trying to work out why my binding wasn't working

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

Similar Threads

Similar Threads

Similar Threads