Workers don't have threads, so you can't run things in parallel. Note that you could do a Promise.

Workers don't have threads, so you can't run things in parallel. Note that you could do a Promise.all() that calls one or more Durable Objects but it wouldn't be a thread per-say, it would be a whole other instance of a DO.

IIsaac McFadyen Workers don't have threads, so you can't run things in parallel. Note that you *...

codebam•12/6/24, 2:59 AM

I don't need multiple, just one more. so I guess I can just await a durable object

codebam•12/6/24, 2:59 AM

can I use that new thing?

codebam•12/6/24, 2:59 AM

can't remember the name

codebam•12/6/24, 3:00 AM

workflows

codebam•12/6/24, 3:01 AM

how can I pass data to a workflow?

codebam•12/6/24, 3:02 AM

and then how do I start it from my other worker

codebam•12/6/24, 3:12 AM

https://developers.cloudflare.com/workflows/get-started/guide/#4-bind-to-your-workflow

how do I pass email and metadata?

codebam•12/6/24, 3:12 AM

can I just pass them in as params of

.create()

.create()

�

𝓈𝒽𝓎•12/6/24, 3:14 AM

when is the next developer updates?

codebam•12/6/24, 3:22 AM

codebam•12/6/24, 3:23 AM

says params doesn't exist on event?

codebam•12/6/24, 3:27 AM

says

codebam•12/6/24, 3:28 AM

it's

event.payload.YourParamName

event.payload.YourParamName

codebam•12/6/24, 3:49 AM

codebam•12/6/24, 3:49 AM

how do I make sure the function returns?

codebam•12/6/24, 3:49 AM

right now it waits too long

codebam•12/6/24, 4:29 AM

figured it out

codebam•12/6/24, 4:29 AM

had to use

ctx.waitUntil()

ctx.waitUntil()

Hebilicious•12/6/24, 9:24 AM

Hello everyone, I discovered a bug while trying to write tests that uses the cache API.
Here's a minimal worker reproduction that can be pasted in the cloudflare playground :

const baseRequest = new Request("http://example.com", { method: "GET" })

export default {
    async fetch(request, env, context) {
        const url = new URL(request.url)
        if (request.method === "POST") {
            const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`)
            const cacheKey = new Request(cacheUrl, baseRequest.clone())
            context.waitUntil(caches.default.delete(cacheKey))
            return new Response("Busted", { status: 201 })
        }

        const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`)
        const cacheKey = new Request(cacheUrl, baseRequest.clone())
        const cache = caches.default
        const cacheResponse = await cache.match(cacheKey)
        if (cacheResponse?.ok) {
            console.log("Returning from cache.")
            return cacheResponse
        }
        const newResponse = new Response("Something")
        newResponse.headers.append("Cache-Control", "s-maxage=3600") // 1 hour
        context.waitUntil(cache.put(cacheKey, newResponse.clone()))
        console.log("Returning Fresh")
        return newResponse
    }
}

const baseRequest = new Request("http://example.com", { method: "GET" })

export default {
    async fetch(request, env, context) {
        const url = new URL(request.url)
        if (request.method === "POST") {
            const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`)
            const cacheKey = new Request(cacheUrl, baseRequest.clone())
            context.waitUntil(caches.default.delete(cacheKey))
            return new Response("Busted", { status: 201 })
        }

        const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`)
        const cacheKey = new Request(cacheUrl, baseRequest.clone())
        const cache = caches.default
        const cacheResponse = await cache.match(cacheKey)
        if (cacheResponse?.ok) {
            console.log("Returning from cache.")
            return cacheResponse
        }
        const newResponse = new Response("Something")
        newResponse.headers.append("Cache-Control", "s-maxage=3600") // 1 hour
        context.waitUntil(cache.put(cacheKey, newResponse.clone()))
        console.log("Returning Fresh")
        return newResponse
    }
}

Over there it works perfectly, the cache gets correctly deleted.
But locally, when running with wrangler dev, it doesn't work (the cache doesn't get deleted).
It also doesn't work when runnning test with vitest-workers-pool T_T

Does anyone has a workaround ?

thols•12/6/24, 10:24 AM

i am using hono as a backend with typescript , i connected the worker with my github repo , whenever i push it needs auto build and deploy ! how to do that ?

Tthols i am using hono as a backend with typescript , i connected the worker with my gi...

Ashley•12/6/24, 10:44 AM

https://developers.cloudflare.com/workers/ci-cd/builds/

Cloudflare Docs

Builds · Cloudflare Workers docs

Use Workers Builds to integrate with Git and automatically build and deploy your Worker when you merge a pull request

johtso•12/6/24, 3:34 PM

should I be able to connect to a postgres database on a remote server from a worker using a zero trust tunnel?

johtso•12/6/24, 3:43 PM

I've created a tunnel but I don't see any way to bind it to my worker..

ᎡᎡᴜᴛʜʟᴇssŦᴀᴄᴛɪᴏɴ Hello, just dropping my feedback that it would be fantastic to see a new feature...

johtso•12/6/24, 3:45 PM

did you find a solution?

Ꭱ

ᎡᴜᴛʜʟᴇssŦᴀᴄᴛɪᴏɴ•12/6/24, 4:46 PM

No I moved on to other projects. The key here is that the CNAME effectively authorizes the traffic, you might try fetching with an overridden Host header but I doubt that works

Ꭱ

ᎡᴜᴛʜʟᴇssŦᴀᴄᴛɪᴏɴ•12/6/24, 4:47 PM

And per your use case don’t think that even fits right

Ꭱ

ᎡᴜᴛʜʟᴇssŦᴀᴄᴛɪᴏɴ•12/6/24, 4:49 PM

I think it’s either create the records or implement your own tunnel directly in the worker

AAshley https://developers.cloudflare.com/workers/ci-cd/builds/

thols•12/6/24, 5:39 PM

while deploying the project , the build is failling !

Tthols while deploying the project , the build is failling !

Ashley•12/6/24, 7:08 PM

With what error?

Xulo•12/6/24, 7:54 PM

Hi, is anyone experienced with using encryption in nodejs on Cloudflare?

I'm working with cloudflare and want to use

createCipheriv

createCipheriv

and

createDecipheriv

createDecipheriv

from the nodejs

crypto

crypto

module.

However, Cloudflare doesn't support these yet as shown in their documentation:
https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/

I get this error:
Error: [unenv] crypto.createCipheriv is not implemented yet!

What alternatives can I use instead?

Thanks in advance!

Cloudflare Docs

Crypto · Cloudflare Workers docs

The node:crypto module provides cryptographic functionality that includes a set of wrappers for OpenSSL's hash, HMAC, cipher, decipher, sign, and verify functions.

XXulo Hi, is anyone experienced with using encryption in nodejs on Cloudflare? I'm ...

Brett Willis•12/6/24, 8:05 PM

Workers supports the Web Crypto APIs. Your equivalents there are

crypto.subtle.encrypt()

crypto.subtle.encrypt()

and

crypto.subtle.decrypt()

crypto.subtle.decrypt()

.
However the Web Crypto API does not support all of the algorithms available on NodeJS.
So it depends on which algorithm you're after but take a look at the docs:
https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/encrypt

MDN Web Docs

SubtleCrypto: encrypt() method - Web APIs | MDN

The encrypt() method of the SubtleCrypto interface encrypts data.

BBrett Willis Workers supports the Web Crypto APIs. Your equivalents there are `crypto.subtle....

Xulo•12/6/24, 8:24 PM

Thanks! I appreciate it, I'll take a look

ᎡᎡᴜᴛʜʟᴇssŦᴀᴄᴛɪᴏɴ No I moved on to other projects. The key here is that the CNAME effectively auth...

johtso•12/6/24, 11:13 PM

aha, this looks promising https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/

Warren•12/7/24, 2:44 AM

I am using Workers in Workflows and I am running up against the 1000 subrequests limit. my question is is there a way to clearly see what are the subrequests made in a Worker?

so for context, my worker is trying to do long running job in batches. the issue is I am using another Durable Object as a rate limiter. the problem with rate limiting is I can’t estimate how frequently the rate limiter will be called in a single worker run.

now that I’ve gotten rid of the rate limiter, it seems to not run into the subrequest issue anymore.

my feedback would be:
- if a Worker in a Workflow has hit the subrequest limit, it seems pointless to retry since any retries would also by definition hit the same limit
- I personally feel that this subrequest limit really dampens the promise of Cloudflare platform being serverless and scales infinitely, esp if it includes calling internal Cloudflare resources like Durable

elpupper•12/7/24, 4:03 AM

Any resources on setting up ci/cd on a remote repository that is not github or gitlabs?

alex (he/him)•12/7/24, 8:24 AM

I really like the new option to start multiple workers with wrangler in the same command. Are there any plans to support multiple primary workers with different ports, to expose their fetch handlers?

BBrett Willis Workers supports the Web Crypto APIs. Your equivalents there are `crypto.subtle....

Xulo•12/7/24, 12:05 PM

Unfortunately this doesn't work for me because I can't use async in my

fromDriver

fromDriver

and

toDriver

toDriver

. I tried using CryptoJS. Is this possible? This works locally, however I get this error in Cloudflare server logs

TypeError: Cannot read properties of undefined (reading 'encrypt')

TypeError: Cannot read properties of undefined (reading 'encrypt')

Am i doing this wrong?

Thanks in advance!

Peps•12/7/24, 5:20 PM

anyone happen to know whether things passed to

waitUntil

waitUntil

will still get to complete if a worker threw a uncaught exception?

XXulo Unfortunately this doesn't work for me because I can't use async in my `fromDriv...

Brett Willis•12/7/24, 5:44 PM

I haven't used CryptoJS, but it looks deprecated. And I haven't used drizzle ORM to tell you if there's a way to do async.
However have you considered returning a plain string type from the ORM, and then having an async helper function to decrypt it in your application code?

Mitya•12/7/24, 10:15 PM

Hi everyone - for some reason, when I set up a hello world Worker, then run it locally via

npm run dev

npm run dev

, I just get a spinning browser tab with no content. Nor do I see any requests come in to my worker in the terminal (other workers show the URI + HTTP code when requests come in.) Repro:
-

npm create cloudflare@latest -- test-worker

npm create cloudflare@latest -- test-worker

- choose the hello world options; lang = JavaScript; deploy/version control = no
-

cd test-worker

cd test-worker

npm run dev

npm run dev

- Wrangler says "Ready on http://127.0.0.1:8787"
- Visit that URL; expecting "Hello world!"; getting the above problem.
Is there a server status issue with CF?

D Trombett•12/7/24, 10:18 PM

npm run dev

npm run dev

runs locally so any problem with CF should be unrelated

Mitya•12/7/24, 10:18 PM

Yeah that's what I thought

Mitya•12/7/24, 10:25 PM

Sorry, false alarm - for some reason my machine failed to release the port when I stopped the worker before, so I had multiple processes claiming port 8787. Killing these solves the problem

BBrett Willis I haven't used CryptoJS, but it looks deprecated. And I haven't used drizzle ORM...

Xulo•12/8/24, 10:27 AM

Yea you are right, CryptoJS is deprecated.

I'm not sure what you mean. Do you mean manually encrypting data before inserting it into the database and then decrypting it when retrieving it? That’s possible but it’s not very practical and can be quite error-prone. But if there is no other way, that's what I can do in the meantime

Here’s what I had before:

This used encryption with

createCipheriv

createCipheriv

and works poerfectly, but unfortunately that’s not supported in Cloudflare

Yash Bindal (yB)•12/8/24, 1:19 PM

Can I create Ai agents with worker
my concern is worker doesn't have that much time

YYash Bindal (yB)Can I create Ai agents with worker my concern is worker doesn't have that much ...

Ashley•12/8/24, 9:01 PM

What do you mean? There’s no limit on Workers for duration, and you’re only charged for CPU time. With AI workflows, you’re primarily waiting on I/O, so you’ll be using very little CPU typically.

AAshley What do you mean? There’s no limit on Workers for duration, and you’re only char...

Hello, I’m Allie!•12/9/24, 12:02 AM

Note that there is a 30 second CPU Time limit, which might be what they were referring to

johtso•12/9/24, 1:19 AM

just set up hyperdrive through a tunnel to a local posgres database, this is amazing!

HHello, I’m Allie!Note that there is a 30 second CPU Time limit, which might be what they were ref...

Isaac McFadyenOP•12/9/24, 1:59 AM

^ and also note that CPU time is not the same as wall clock time

Jjohtso just set up hyperdrive through a tunnel to a local posgres database, this is ama...

Yash Bindal (yB)•12/9/24, 3:08 AM

const baseRequest = new Request("http://example.com", { method: "GET" }) export default { async fetch(request, env, context) { const url = new URL(request.url) if (request.method === "POST") { const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`) const cacheKey = new Request(cacheUrl, baseRequest.clone()) context.waitUntil(caches.default.delete(cacheKey)) return new Response("Busted", { status: 201 }) } const cacheUrl = new URL(`http://cache.key/custom${url.pathname}`) const cacheKey = new Request(cacheUrl, baseRequest.clone()) const cache = caches.default const cacheResponse = await cache.match(cacheKey) if (cacheResponse?.ok) { console.log("Returning from cache.") return cacheResponse } const newResponse = new Response("Something") newResponse.headers.append("Cache-Control", "s-maxage=3600") // 1 hour context.waitUntil(cache.put(cacheKey, newResponse.clone())) console.log("Returning Fresh") return newResponse } }

Workers don't have threads, so you can't run things in parallel. Note that you could do a Promise.

Similar Threads

Similar Threads

Similar Threads

Workers don't have threads, so you can't run things in parallel. Note that you *could* do a Promise.

Similar Threads

Similar Threads

Similar Threads

Workers don't have threads, so you can't run things in parallel. Note that you could do a Promise.