I just tried for a long time, I can't use the worker to download any discord media, as long as the GET discord media will have such a message

This content is no longer available.

I can download locally

But I am using fetch in worker Use node's http/https locally

Cloudflare Workers are blocked from non-ephemeral Discord CDN media due to abuse

That's right, thank you

this is bad news

Hey i got an error with cron events and the Placement mode if i set the placement to smart mode in my dashboard and also in the wrangler.toml my cron events dont work anymore. at the "default" mode all works fine 🤔 you can see in the logs of the cron events there is a big gab but i only changed the mod and published my worker. is that an known bug or maybe do i have to change something else to make cron events work again?

The databases are super cool! If I'm already using supabase via supabae-js, is there significant benefit to add this integration to my worker now via the cloudflare integrations thing?

Is this still a thing

It's been quite a long time already

It unfortunately didn't take off. You might be interested in http://blog.cloudflare.com/introducing-constellation/ though!

Ohh it's quite recent

Gotta check it out

Yep! We're in developer week, tons of cool stuff coming out in #892058508097388544

I am honestly excited about it

But it runs on conventional cpu right ?

yeah, you can ask things in #1105477009964027914 but apparently it's a CPU worker yup

can you reload the dash and try again?

yep i tried that, i let it run on the mode "smart" for the last hour but didnt worked, after i switched back to normal all was fine again, my workers are working perfect all is good but the cron is not triggered or working 🤷‍♂️ the logs shows nothing for the crons but i didnt remove it or changed anything. i just set the mode to smart in the wrangler.toml (my wrangler is also updated etc) and im very sure that the crons not working 100% 🤔

i also tried to add the cron again after i enabled smart mode 🤷‍♂️ i send always after i enabled it some requests to my worker

Very excited that smart placement is in open beta 🙂 > Fine-tuned placement (e.g. if your Worker uses multiple back-ends depending on the path. We calculate the optimal placement per path instead of per-Worker) Can’t wait for this!

hmm ok i'm able to repro - @mhart @tanushree

Just to clarify – is this setting mode = "smart" on the cron worker?

Not sure if we mention this in the docs – but we don't consider fetches from cron triggers in the smart placement analysis. Cron triggers are more of an out-of-band action – whereas Smart Placement is more intended for realtime latency-sensitive actions. That said, we should mention that explicitly in the docs, and also we definitely shouldn't stop the cron from triggering, so I'll look into that. Thanks for the report!

ooh, cloudflares got some ai stuff now for workers..

wonder how long it'll be until it can tts/stt

testing locally using queues, i am getting message.ack is not a function. body, id, and timestamp properties are there. do i need to use experimental?

oh wow.. https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/ yay

hm, so i tested with experimental local and various things break, so i am hoping the non-experimental version is more accurate. for example: when using the non-experimental version, i have to pipe uploads through a transform in order to put to r2 (probably due to a bug in miniflare), or i get an error. using the experimental version, if i pipe through the same transform, i get an error saying "readable stream must have a known length" (again, probably due to a bug in miniflare, as there is no apparent way of specifying a length manually). at this point, i don't know if i should use a transform or not for live, as both methods should probably be working (with and without a transform). this all appears to be extremely alpha (both experimental and non-experimental version), and i'm a bit surprised by that. i'm further suprised that miniflare wasn't even started by cloudflare, as one would think the need for local development would have been understood from the onset. anyway, i request cloudflare invest more resources into miniflare, as the current robustness is about what i would expect from an individual's hobby project (perhaps even worse).