AIs this still an issue that's somehow hidden now? I don't have Smart placement turned on (it's on "default") but I am still getting this error when I should not be. https://community.cloudflare.com/t/smart-placement-breaks-durable-object-rpc/654797
Snot impossible but not recommended anyway workers-and-pages-discussions
Sbut it would require you to change the built code
SThanks! Makes sense.
FHi
In WSL open devtools does not pop up anything, other commands work fine.
Did anyone run into this?
In WSL open devtools does not pop up anything, other commands work fine.
Did anyone run into this?
GI use Durable Objects in remix and I made it so there is a backend worker handling the Durable Object for each customer (they get a unique instance each), and the remix app uses RPC to interface with the worker
SGdispose the stub?
S
GI don't explicitly manage it because the durable object runs on alarms until it completes the queued work
Ggenerally it could be as few as one task to tens of thousands, and remix is not designed for managing that nor would it really make sense given the context
Swell its still good practice and sadly dosent really work in that environment
Glikely, but we only use the RPC to initiate the worker so we end the context very quickly and the documentation says that automatically disposes of it
Gdoing it cleanly is always ideal, but using remix with bindings wasn't super well documentated from what I could find
GI'd love if cloudflare had official demos for these platforms with remix next js etc, showing basic things like database bindings, r2 access etc
FHey all! Do you know of any observability service that could show spans across a worker and a DO? I know baselime used to be the best option in past but idk what the latest is on that since acquisition.
AI have not tried it but I do know Sentry recently released DO support which looks like it supports connected traces: https://github.com/getsentry/sentry-javascript/pull/16180
FThis is coool!
CI'm using Vercel's AI SDK, specifically the streamText function along with createDataStreamResponse, to send custom streaming data. I'd like to integrate this with a Cloudflare WebSocket setup using Durable Objects. What would be the best approach to achieve this integration?
CHi all, whenever I try to write to Durable Object I have in live preview of the logs:
"executionModel": "durableObject", "outcome": "canceled",
CIs there any way to get the information why?
EHey,
I believe I've found a prod vs local discrepancy with Durable Objects - where would I go about reporting this?
I believe I've found a prod vs local discrepancy with Durable Objects - where would I go about reporting this?
LCreate a github issue in the wrangler repo if by local you mean
wranglerThanks - well actually things work as expected locally, just not in prod
LDescribe the issue here, then. Without knowing what the discrepancy is I can't help.
EOk so it does trigger in production 
I think some code is erroring but I've no idea where logs are if an alarm throws an error
I think some code is erroring but I've no idea where logs are if an alarm throws an errorLYou can enable Observability logs for your worker project and you will be able to see your logs in the cloudflare dashboard. https://developers.cloudflare.com/workers/observability/logs/workers-logs/#enable-workers-logs
EHmm, I do have that enabled, but I've just seen what's happening:
- I have an endpoint setup which I am calling which accesses the DO (to logs the alarm)
- If I don't call this endpoint, the alarm doesn't trigger
- If I then call the endpoint, the alarm triggers - so accessing the DO seems to kick it off
EAnd I can see the RPC call which kicks it off includes the logs of the alarm call
ME@lambrospetrou @Milan
Ok so finally figured it out, I think:
My alarm calls a function which is outside of the class (import function) which does an external async fetch call.
If that function thows an error (e.g. ) then the alarm just dies and no logs appear in console (hence me thinking it wasn't being triggered)
If I catch the error inline within the alarm and return early, the alarm logs show up
So my issue was that I didn't think the alarm was being triggered because the alarm swallowed the errors/logs
Ok so finally figured it out, I think:
My alarm calls a function which is outside of the class (import function) which does an external async fetch call.
If that function thows an error (e.g. ) then the alarm just dies and no logs appear in console (hence me thinking it wasn't being triggered)
If I catch the error inline within the alarm and return early, the alarm logs show up
So my issue was that I didn't think the alarm was being triggered because the alarm swallowed the errors/logs
LYeah, as a guideline anything you do inside the handler should be wrapped in a try-catch.
EOk I've boiled the issue down to the following:
This is taken from; https://orm.drizzle.team/docs/connect-cloudflare-do
Seems like when the alarm tries to init the DO, it just explodes for some reason trying to the migration
This is taken from; https://orm.drizzle.team/docs/connect-cloudflare-do
Seems like when the alarm tries to init the DO, it just explodes for some reason trying to the migration
Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.
EThe above was just a red herring it seems 
JIs there a way to “re-instantiate” a specific do?
1What do you mean by that exactly? you can delete its storage which essentially resets it
Jtheres some DOs that just give "internal error; reference = moh644b953d9vckab1seqm9a" and I cant access it at all
Jlike i want to delete them and re-make it from scratch
1Is that just by running the constructor? What is the instance trying to do when it errors like that
1You can only delete them from within
VDoes anyone know the exact error message when a SQLite DO exceeds the 10gb of storage?
VI made a random generator and filled a local DO, but it appears wrangler local doesn't simulate the 10GB cap
Smy guess is RangeError 
Pcould look at databaseSize
AHello, I'm looking at using Durable Objects as a Websocket server. I'm a bit confused by the Hibernate API, and this SO post.
My confusion is that I thought the whole point of DO was to be a "stateful worker". But this comment seems to claim the opposite (might just be bogus). That said, the docs also claim that:
Am I misunderstanding the point of DOs? Or is this just an edge case with the hibernate API and I should use / to store persistent state?
Since DurableObjects are basically in-memory classes, their long-term state cannot be guaranteed - especially in cases which involve the Hibernation API. When the DurableObject hibernates, the existing websocket connections are kept alive "outside" of the class - and when one wakes up, the Workers runtime will reinstantiate the DurableObject with a new state.
My confusion is that I thought the whole point of DO was to be a "stateful worker". But this comment seems to claim the opposite (might just be bogus). That said, the docs also claim that:
// ... During periods of inactivity, the Durable Object can be evicted
// from memory, but the WebSocket connection will remain open. If at some later point the
// WebSocket receives a message, the runtime will recreate the Durable Object
// (run the ) and deliver the message to the appropriate handler.
Am I misunderstanding the point of DOs? Or is this just an edge case with the hibernate API and I should use / to store persistent state?
UDurable objects are not exclusive in memory storage and can absolutely store stuff permanently (that is indeed the entire point of them wouldnt be durable otherwise).
The attachments on a websocket connection will exist as long as the client is connected regardless of the DO being evicted and then reinstated down the line. However, if the client disconnects then the attachment will go away.
You can use memory only state that doesnt get durably stored if you wanted but you can also use durable storage.
The attachments on a websocket connection will exist as long as the client is connected regardless of the DO being evicted and then reinstated down the line. However, if the client disconnects then the attachment will go away.
You can use memory only state that doesnt get durably stored if you wanted but you can also use durable storage.
AAh I see. Seems the bit I was missing is that that durable storage is separate from the memory state. RTFM I guess. Thanks for the help.
Vif a durable object is "hot" (so if i was to make a new request now the constructor would not run) and I deploy a new version in the meantime, would the constructor run again (kinda like "shutting down" the DO)?