Cloudflare Developers•2y ago

do workers literally just not work now?

Mr. GoodmanOP•7/6/24, 9:20 AM

with wrangler

anirudh•7/6/24, 11:22 AM

Has there been any further news about (Durable) Workflows that was announced in the Developer Week in April?

MMr. Goodman do workers literally just not work now?

Cyb3r-Jak3•7/6/24, 2:14 PM

What do you mean by not work?

Old Man Maker•7/7/24, 1:58 PM

hey is it just me or was CORS removed from Workers settings?

kian•7/7/24, 2:00 PM

I don't recall CORS ever being a Workers setting :meowthinking:

Old Man Maker•7/7/24, 2:00 PM

Yeah come to think of it - maybe it was R2 or something like that?

Old Man Maker•7/7/24, 2:01 PM

Either way, getting CORS responses on a worker request

Old Man Maker•7/7/24, 2:01 PM

strict-origin-when-cross-origin

Old Man Maker•7/7/24, 2:01 PM

I've got hono implemented with Cors

Old Man Maker•7/7/24, 2:01 PM

app.use('/api/*', cors())

Bing Crosby•7/7/24, 2:49 PM

How can I send a message reply from an application command using my Discord Bot which runs using a worker to a specific channel? i.e. as part of the application command I ask for the parameter of a channel to be given, and I want the bot to then submit a response in that given channel.

brighter•7/7/24, 7:47 PM

Hey there.

Is there a way to perform a differential update of worker settings?

For example, I'd like to dynamically bind a setting like so:

curl -s --request PATCH \
  --url https://api.cloudflare.com/client/v4/accounts/xxx/workers/scripts/yyy/settings \
  --header 'Authorization: Bearer zzz' \
  --header 'Content-Type: multipart/form-data' \
  --form 'settings={"bindings":[{"id":"1","name":"DB_1","type":"d1"}]}'

curl -s --request PATCH \
  --url https://api.cloudflare.com/client/v4/accounts/xxx/workers/scripts/yyy/settings \
  --header 'Authorization: Bearer zzz' \
  --header 'Content-Type: multipart/form-data' \
  --form 'settings={"bindings":[{"id":"1","name":"DB_1","type":"d1"}]}'

However, this method overrides any previously set bindings. Retrieving all current bindings and adding a new one is another approach, but this will eventually fail due to the max body size limit, so I'm looking for another way of doing this and/or new ideas.

Bbrighter Hey there. Is there a way to perform a differential update of worker settings? ...

Hello, I’m Allie!•7/7/24, 7:48 PM

I think that is the solution, for now anyway. You would also still hit the size limit, because there is a max size limit for bindings(I think it is 1 MB)

brighter•7/7/24, 7:49 PM

I see. Thanks.

brighter•7/7/24, 7:50 PM

I guess another approach would be querying D1 via the REST API (https://developers.cloudflare.com/api/operations/cloudflare-d1-raw-database-query).

Bbrighter I guess another approach would be querying D1 via the REST API (https://develope...

Hello, I’m Allie!•7/7/24, 7:50 PM

Yes, though note that this can be much slower

brighter•7/7/24, 7:50 PM

That's what I was afraid of.

brighter•7/7/24, 7:52 PM

I really don't want to create a worker-d1 pair for every tenant, so ... back to the drawing board.

BBing Crosby How can I send a message reply from an application command using my Discord Bot ...

Bing Crosby•7/7/24, 8:23 PM

To follow up on this, is it even possible? Or can the bot only respond in the text channel where the application command was triggered from?

BBing Crosby To follow up on this, is it even possible? Or can the bot only respond in the te...

Hello, I’m Allie!•7/7/24, 8:33 PM

If your bot has message send permissions, then yes

user•7/8/24, 4:18 PM

just double checking, ctx.waitUntil executes the promise after the worker returns, right?

user•7/8/24, 4:29 PM

hmm

user•7/8/24, 4:29 PM

is there a way to make it so the code executes after it returns?

user•7/8/24, 4:30 PM

like a promise for request finished or whatever

user•7/8/24, 4:30 PM

I'm trying to make it so my http interactions bot edits the message after initially acknowledging it

Original message was deleted

user•7/8/24, 4:30 PM

was just typing that out haha

user•7/8/24, 4:31 PM

uhhh, I'm not sure how I'd do that with how my structure is rn

user•7/8/24, 4:32 PM

I'm just doing it how I saw others do it lol

user•7/8/24, 4:32 PM

export default {
    async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) {
        const url = new URL(request.url);

        if (url.pathname !== "/interactions") {
            return Response.redirect(
                "https://github.com/User9684/user-utils",
                301
            );
        }

        const verified = await VerifyRequest(request, env);
        if (!verified) {
            return new Response("erm, no???", {
                status: 401,
            });
        }

        const requestBody: Interaction = await request.json();

        ctx.waitUntil(await (async () => {

        })())

        return Response.json({
            type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE
        })
    },
};

export default {
    async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) {
        const url = new URL(request.url);

        if (url.pathname !== "/interactions") {
            return Response.redirect(
                "https://github.com/User9684/user-utils",
                301
            );
        }

        const verified = await VerifyRequest(request, env);
        if (!verified) {
            return new Response("erm, no???", {
                status: 401,
            });
        }

        const requestBody: Interaction = await request.json();

        ctx.waitUntil(await (async () => {

        })())

        return Response.json({
            type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE
        })
    },
};

user•7/8/24, 4:32 PM

ignore the insanely wrong usage of waitUntil

Original message was deleted

user•7/8/24, 4:32 PM

oh sorry I read this wrong

user•7/8/24, 4:32 PM

dyslexia

user•7/8/24, 4:33 PM

read it as waituntil after returning haha

user•7/8/24, 4:33 PM

well I don't even need to do that haha

user•7/8/24, 4:34 PM

i should just need to do waitUntil(handleInteraction) i believe

user•7/8/24, 4:34 PM

considering the edit happens there :p

user•7/8/24, 4:35 PM

yeah lol its too long for a small snippet of code

user•7/8/24, 4:35 PM

didnt wanna flood too bad

Original message was deleted

user•7/8/24, 4:37 PM

also isnt this incorrect syntax?

user•7/8/24, 4:37 PM

still a bit unsure on waitUntil syntax but the typechecker yells at me for that :p

Original message was deleted

user•7/8/24, 5:17 PM

yeah

user•7/8/24, 5:17 PM

user•7/8/24, 5:18 PM

but thats not my issue rn so its whatever lol

EEisenbergEffect When I create a new application via the Cloudflare dashboard, I see the option t...

Chaika•7/9/24, 2:21 AM

Can use something like : https://github.com/cloudflare/wrangler-action
Longer term convergence of Pages and Workers is planned: https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler#:~:text=Workers%20CI/CD.%20Later%20this%20year%2C%20we%20plan%20to%20bring%20the%20CI/CD%20system%20from%20Cloudflare%20Pages%20to%20Cloudflare%20Workers.%20Connect%20your%20repositories%20to%20Cloudflare%20and%20trigger%20builds%20for%20your%20Workers%20with%20every%20commit.

GitHub

GitHub - cloudflare/wrangler-action: 🧙‍♀️ easily deploy cloudflare ...

easily deploy cloudflare workers applications using wrangler and github actions - cloudflare/wrangler-action

The Cloudflare Blog

Announcing Pages support for monorepos, wrangler.toml, database int...

Today, we’re launching four improvements to Pages that bring functionality previously restricted to Workers, with the goal of unifying the development experience between the two. Support for monorepos, wrangler.toml, new additions to Next.js support and database integrations!

Coshmar Tabletowy V•7/9/24, 12:01 PM

Hi all, anyone is experiencing issue with .workers.dev and .pages.dev subdomains?

Coshmar Tabletowy V•7/9/24, 12:01 PM

it seems I am unable to resolve my domains today at all

Erisa•7/9/24, 12:25 PM

Probably your isp or country misunderstanding how public suffixes work and blocking them

fletcher3•7/9/24, 2:34 PM

Hi there. I would really love to use the new Rate Limiting service for my Cloudflare Pages next.js app in some route handlers. Could you already give an estimation on if and when the beta will be accessible as a binding for cloudflare pages and when it will move out of beta. Thank you and keep building :))

freerangebella•7/10/24, 4:18 AM

Hi I have some questions about workers - if I have a backend python process that typically takes 3-4 minutes could that scale well with workers, or would it quickly get to be too expensive? I'm not sure I understand how this would work with the pricing model. It's an image processing thing and I'm not sure I can do much more to optimize it

curl -s --request PATCH \ --url https://api.cloudflare.com/client/v4/accounts/xxx/workers/scripts/yyy/settings \ --header 'Authorization: Bearer zzz' \ --header 'Content-Type: multipart/form-data' \ --form 'settings={"bindings":[{"id":"1","name":"DB_1","type":"d1"}]}'

export default { async fetch(request: Request, env: Env, ctx:EventContext<Env,any,any>) { const url = new URL(request.url); if (url.pathname !== "/interactions") { return Response.redirect( "https://github.com/User9684/user-utils", 301 ); } const verified = await VerifyRequest(request, env); if (!verified) { return new Response("erm, no???", { status: 401, }); } const requestBody: Interaction = await request.json(); ctx.waitUntil(await (async () => { })()) return Response.json({ type: CallbackType.DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE }) }, };