Yeah

You'll need to run both workers at the same time with

--local

on both

Strange. Still the same.

As I haven't used that feature yet, that's what my schedule worker is showing:

▲ [WARNING] This worker is bound to live services: someBinding (someServiceName)


Your worker has access to the following bindings:
- Services:
  - someBinding: someServiceName
▲ [WARNING] ⎔ Support for service bindings in local mode is experimental and may change.

Neither of these workers have been deployed yet, all pure local.

Ah... https://github.com/cloudflare/workers-sdk/issues/1612 there we go...

I've been using workers for a bit in a couple of projects, but now I'm planning a new project and I need to dive into storage options. Put simply, I'm working on a CMS of sorts. I need the user to create and edit their content (e.g. markdown) and present that to the web in html. My initial plan (to avoid repassing the markdown each request) would be to store the built version in kv and have the source in either r2 or some other storage bucket sort of thing (as it's less frequently accessed). Curious to hear if I'm on the right track, or if there's potentially another good way of doing this

is it just me, or are Environments not quite working yet? I've tried to set up staging and production deployments using Wrangler, but I'm seeing two separate workers services published, both with the environment "production". Could I just be reading out-of-date docs?

Too bad that D1 cannot be added directly from Variables at the worker level. Need wrangler to bind worker with D1... 😦

That's just part of it being an alpha, it'll change before GA

If I’m reading the docs right, for a given request, all workers bound as service bindings use the same process/thread? So if I have a request that is processing some inbound data, there is no benefit to splitting the data into chunks and farming out to service bindings right? It would not “parallelize”, rather they would all be processed serially on the same thread anyways right?

Nope. You could do this with #1008691665688604783 or #773219443911819284 instead.

Howdy folks!

Did anyone ever see this notification next to the Cron Triggers for a Worker:

Scheduled listener defined but not in use

?

It's puzzling me, but I can indeed see the cron is not executed. It's a new worker and I am unsure what may cause it to not be executed 🤔

Do you have any cron triggers?

Yes

Could you show the ones configured in your dashboard?

Ah.. hold on..

Yeah, that is the issue indeed. They are not shown

It's in my wrangler.toml file though..

How are they defined in there?

But apparently that is not working 🤔

Oh my.. nevermind.. I think I just made a fool of myself 😅

I simply published a different worker.. That is why it did not work

Ah, well I'm glad you figured it out 😄

The updated toml file has not been published..

Thanks! 😅

Did getAll('set-cookie') stop working for anyone else? It started parsing it incorrectly and just gave an big string with all the cookies

Do you have an example

Set-Cookie

header that's causing it?

Thanks for confirming. I may just opt for workers unbound to keep it simple if I do end up going beyond the execution limit, since otherwise I would probably have to put the data into R2 temporarily, then queue the jobs, handle errors, etc.