You just make a service binding which references the same worker
You just make a service binding which references the same worker
wrangler dev --env dev and all other bindings (durable objects, other workers, queues) work as expected.wakeupType property, that we start as the empty string. The possible reasons for a wakeup are (1) a fetch, (2) a websocket message, or (3) an alarm. Each of these comes through a single entry point (whereas allowing incoming RPC calls muddies that, so we've put those back to being fetches). When any of those points is hit while the wakeupType is still empty we set the type accordingly, and that determines how we handle log output for the rest of that wakeup.transactionSync() https://developers.cloudflare.com/durable-objects/api/storage-api/#transactionsync if you want to control when the writes happen.

tickets and policies have a many-to-many relationmy-do-uuid/0 for the first one. You would then run a stub.hasMoreShards() and if that returns true you'll move on to my-do-uuid/1 and so on. I would have to set that flag myself, but it's not that difficult to do.event-uuid/0. Finds nothing by running an SQL query. Sees that calling hasMoreShards() on that stub returns true. Goes to event-uuid/1 and does the same.
partysocket to listen for updates on a bunch of sockets but want to check if there are any implementation quirks I should be aware ofAlarms have guaranteed at-least-once execution and are retried automatically when the alarm() handler throws.
wrangler dev --env dev[[env.dev.services]]
binding = "MY-BINDING"
service = "my-worker-name-dev"wakeupTypewakeupTypetransactionSync()ticketspoliciesmy-do-uuid/0stub.hasMoreShards()truetruemy-do-uuid/1event-uuid/0hasMoreShards()event-uuid/1partysocket