1
DurableObjectID, using DurableObjectStorageGroups (can't remember exact name of that, but it's something like that) to be able to see which instances are using storage1AccountDurableObjectsSqlStorageGroups for SQL DOs and AccountDurableObjectsStorageGroups for KV DOs
J
transactionSync()JfetchtransactionSync it should deadlock, since it needs the response to complete the transaction, and the request needs to wait for the Output gate to be open
L
J
transaction() callbackJLtransaction() and it throws?
LL
transactionSync myself either. It should work with transaction though.
EL
runDurableObjectAlarm() which will trigger your handler but not simulate time passing. I have also released https://lumenize.com/docs/testing/alarm-simulation, which will speed up time 100x and simulate alarms running. It works great so long as you avoid a thundering herd, which is quite easy to do at 100x. You can slow it down to 1x though.LELE1LLL
Mctx.storage.deleteAll() in a hibernated or non-hibernated Durable Object gonna also disconnect all clients attached to it? Or is just cleaning the storage (kv, sqlite)?LL1A1A1A1
fetch()WebSocket()ing the URL? Try the other option to whatever you're using nowA11A11AA
SSLSASLS
L
GL
P
DurableObjectIDAccountDurableObjectsSqlStorageGroupsAccountDurableObjectsStorageGroupstransactionSync()transactionSynctransactionSynctransaction()transaction()transactionrunDurableObjectAlarm()ctx.storage.deleteAll()WebSocket()