Just found a workaround, in Workers « Default Usage Model », even if you don't want "unbound" as the default usage models, change it one time on unbound, this activate it on your account, then you can re-turn again on « Default Usage Model » to change it back to « bundled » if it's your preference like us.

hello everyone

Most likely you're trying to use Unbound and have a legacy plan that doesn't support unbound. If you're an Enterprise customer you'll have to contact your account team, if not then there should be a prompt somewhere on the dashboard to enable Unbound

Oh seeing this now, yeah, that sounds like it would work

Just discovered that workers can be run as cron jobs and wow this is such an amazing feature!

Has anyone ever come accross the error

Trace: TypeError: Found invalid object in transferList

when caching a response? The code I have is

typescript
if (response.status !== 404) {
        response.headers.set("cache-control", "max-age=3600")
        c.executionCtx.waitUntil(cache.put(req, response.clone()))
    }

and if I comment it out then I don't get the error. It only happens on this one endpoint

Found it: https://github.com/cloudflare/miniflare/issues/527

Oh good, I've been seeing this all over my dev today and assumed it was related to an update of something. Didn't have chance to dig-in yet though

my gut tells me this is a mitigation for a dangling arraybuffer issue lol

are you using node_compat mode?

Nope

Hey, can anyone help with ingesting cf-worker's logs in datadog ? I have tried logpush but that is ingesting all trace events, but we just want logs and exceptions. I'm trying out log-forwarding using winston, but facing issue in running code locally. Any help is appreciated .

Hi, Is it possible to create TCP sockets in workers? I want to send something directly to a syslog server.

not yet, that feature is in development

Probably best to ask in #1041788765783474216 🙂

👋 Hey folks, is there any news regarding workers services environments? I am referring to https://blog.cloudflare.com/introducing-worker-services/

I believe they're currently fleshing out the new Deployments system, with the goal of building environments on top of that

Stuff like being able to rollback to a specific deployment, etc. is coming first

I'd like to execute a worker every X minutes to sync an R2 bucket from a remote (with scp, for example), but with files sizes in the order of MBs, I'll hit the worker time limit. Is there any other way to approach this that doesn't involve using something like a Github/Gitlab action to upload?

How often is X?

If it's an hour or more, your crons can run for 15 minutes continuously

It can be an hour, yes

Awesome, I believe you'll need to set it to unbound mode, meaning you're billed for running duration as opposed to a counter of 1 per request, but beyond that you should be good!

and with the official shoutout on the blog today, I think Hono wins 🙂

Hi. Is there any additional network limits applied to a cron worker, compared to an ordinary worker invoked by an outside request? I get a strange 404 from my cron worker. The cron worker does a request to another worker through a service binding, which in turn tries to do a request to an external api. The fetch request to the external api fails with 404 when invoked from the cron worker. But if i trigger this from the outside (Postman for example) it will succeed.

There is nothing that'd cause a Scheduled Event to be 404'd and a Fetch Event not to be 404'd

Is there a channel to post small jobs around Workers? Or is this the right place I would need someone to convert to wrangler@2 and cleanup a GitHub repo and Actions.

Lack of time for myself.

Kian: Ok interesting. This problem reminds me of when I tried to make fetch request directly to other workers within the same zone. The external API in this case is actually done through a proxy worker within the same zone. But I understand you are saying that there should be no difference depending on how it's triggered

Fetching same-zone as in custom routes or workers.dev?