It should be open to everyone now, so refresh your dashboards if you don't see it 😅

Llambrospetrou It should be open to everyone now, so refresh your dashboards if you don't see i...

G

gruntlord6•10/16/25, 2:49 PM

any chance you guys are looking at adding the bulk table dropping like the outerbase client had? or at least a way to not have to put in every table name when dropping multiple independently?

B

Brayden•10/16/25, 2:55 PM

told you guys it'd be here "next week"

hope you all enjoy it!!

B

Burrito•10/16/25, 3:07 PM

Is there a way to limit data studio to read only operations?

B

Burrito•10/16/25, 3:22 PM

It would also be nice to have better FTS support, currently they just show as

[object Object]

[object Object]

[object Object]

[object Object].

M

mvgrim•10/16/25, 3:26 PM

Also, seems like the Data Studio doesn't expose KV store data that is backed by the SQLite backend. Would be good to have an ability to query that data. I have some durable objects that use the new SQLite backing, but use the KV store API for its simplicity. I know those drop into a different table/DB in the SQLite store, but it's not exposed in Data Studio.

BBurrito It would also be nice to have better FTS support, currently they just show as `[...

V

Visal .In•10/16/25, 5:22 PM

Will work on it.

VVisal .In Will work on it. 🙂

P

Peps•10/16/25, 9:44 PM

Hey

If you're an Cloudflare employee, any chance you could do the

/cfrole

/cfrole

/cfrole

/cfrole command to get the official employee role? It'll make it more clear you're part of the team

Xxormask I'm sure this is a commonly asked question, but what is my best solution for loc...

L

Larry•10/16/25, 10:27 PM

I just released

@lumenize/testing

@lumenize/testing

@lumenize/testing

@lumenize/testing which builds on

cloudflare:test

cloudflare:test

cloudflare:test

cloudflare:test vitest integration. See: https://lumenize.com/docs/testing/usage#basic-usage. Example:

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

it('shows basic 5-step test', async () => {
  // 1. Create RPC testing client and Browser instance
  await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
  const browser = new Browser();

  // 2. Pre-populate storage via RPC to call asycn KV API
  await client.ctx.storage.put('count', 10);

  // 3. Make a fetch and RPC call to increment
  const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
  const rpcResult = await client.increment();

  // 4. Confirm that results are as expected
  expect(await resp.text()).toBe('11');
  expect(rpcResult).toBe(12);  // Notice this is a number not a string

  // 5. Verify that storage is correct via RPC
  expect(await client.ctx.storage.kv.get('count')).toBe(12);
});

Let me know what you think or if you have any questions.

Usage | Lumenize

Doc-testing – Why do these examples look like tests?

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

1

1984 Ford Laser•10/16/25, 10:30 PM

Glad to see the CORS support here! That was something I had just run into with

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin so this is a prefect time for the release. Will definitely take a look

11984 Ford Laser Glad to see the CORS support here! That was something I had just run into with `...

L

Larry•10/16/25, 10:38 PM

You can use my

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin package with my advanced CORS supporting

routeDORequest

routeDORequest

routeDORequest

routeDORequest. I recommend the whitelist approach. See: https://lumenize.com/docs/utils/route-do-request#cors-support

However, the latest version of

routeAgentRequest

routeAgentRequest

routeAgentRequest

routeAgentRequest which is what

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin shows using in the docs has all or nothing CORS support. The third parameter is a config object and

{ cors: true }

{ cors: true }

{ cors: true }

{ cors: true } will allow all cross origins.

Request Routing | Lumenize

Route HTTP and WebSocket requests to Durable Objects with authentication hooks

LLarry You can use my `json-rpc-mixin` package with my advanced CORS supporting `routeD...

1

1984 Ford Laser•10/16/25, 10:40 PM

I plan to move entirely off of

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin

json-rpc-mixin and onto

lumenize

lumenize

lumenize

lumenize anyway so that I can remove the

agents

agents

agents

agents dependency, but good to know

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

L

lambrospetrouOP•10/17/25, 5:41 AM

Congrats on the release! Docs are looking good. Will try it out soon for my projects too.

Mmvgrim Also, seems like the Data Studio doesn't expose KV store data that is backed by ...

V

Vy•10/17/25, 3:34 PM

We have more work to expose KV data as read-only. Good to know there's a want here

P

PhoenixSpace•10/17/25, 7:33 PM

Is there any publicly available benchmarks on durable object size vs startup time? I'm storing a lot of data in durable objects transiently (~30gb, will be sharded over multiple obviously), and latency is a concern. Sharding isn't a big deal, but I don't want to pre-emptively overshard for no reason.

LLarry I just released `@lumenize/testing` which builds on `cloudflare:test` vitest int...

X

xormask•10/17/25, 9:53 PM

This looks awesome. Is the setup for using this in a multi-worker situation the same as with the vitest integration? (Precompile typescript to JS and then manually configure the secondary workers with miniflare?)

VVy We have more work to expose KV data as read-only. Good to know there's a want he...

1

1984 Ford Laser•10/17/25, 11:01 PM

I would totally use this too

LLarry You can use my `json-rpc-mixin` package with my advanced CORS supporting `routeD...

1

1984 Ford Laser•10/17/25, 11:02 PM

So I realised that this behaviour with CORS in the

agents

agents

agents

agents SDK isn't documented anywhere in the docs except for the changelog where it was introduced

11984 Ford Laser So I realised that this behaviour with CORS in the `agents` SDK isn't documented...

L

Larry•10/17/25, 11:37 PM

That's one of the problems with

agents

agents

agents

agents. The team has traditionally not consider docs (or quality, responsiveness on Discord, etc.) important although they say they are working on improving them. Also, it must be said that they have always had a great API design, even if you have to crawl in the code to discern it.

I have crawled around in their code and my docs on how CORS behavior works

{ cors: false}

{ cors: false}

{ cors: false}

{ cors: false} default and

{ cors: true }

{ cors: true }

{ cors: true }

{ cors: true } allow everything, are accurate for routeAgentRequest but I recommend strongly against using if you are using WebSockets. They don't support the whitelist or custom validation function modes that mine does.

E

Elijah Bowie•10/18/25, 3:23 PM

Has anyone successfully been able to use Sandbox? https://sandbox.cloudflare.com/

Been up all night.

Issue: Sandbox Sandbox SDK returning placeholder mode despite correct configuration
"Agent provisioned in placeholder mode (Cloudflare Sandbox API not configured)."

When my worker calls Sandbox.create it falls back to “placeholder mode” because the binding isn’t populated (runtime logs show Agent provisioned in placeholder mode (Cloudflare Sandbox API not configured)). It looks like Containers access hasn’t been enabled on my account yet.

Sandbox SDK

Run sandboxed code environments on Cloudflare's edge network

S

SuperHelpflare•10/18/25, 3:30 PM

Please do not post your question in multiple channels/post it multiple times per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

J

jonast•10/18/25, 7:44 PM

i noticed that errors thrown from functions called across a workers RPC boundary don't contain the original stack trace (for example when calling a function on a durable object stub or a service binding)

the serialized error that crosses the RPC boundary only contains the error message but not the stack

i'd really like to retain the original stack trace. what's a good pattern for doing that? stuff the stack trace in the message? or could i throw a custom error with the stack trace serialized in a property? would that cross the RPC boundary?

and is there a place where i can intercept any errors thrown out of the RPC boundary from the callee's side?

N

Nico•10/19/25, 5:05 AM

I'm working on an app where I use DO per user model. Given the release of data studio, allowing the inspection of a DO's SQLite storage, is there a way to assure users that I CAN'T inspect the state of their DO's state? Basically, can I limit access to data studio?

NNico I'm working on an app where I use DO per user model. Given the release of data s...

G

geg•10/19/25, 9:03 AM

client side encryption

Ggeg client side encryption

G

gruntlord6•10/19/25, 1:36 PM

even then since you control the code you could still snoop

V

Vlad Lykhonis•10/19/25, 7:30 PM

Hi, any decent approach or documentation how to make sure or what guarantees a DO instance won’t hibernate while there is a logical task executing (in most cases involving IO)? Some clarity on this topic would help me design system properly. Currently hacking via repeated alarms , reminds me old times Android keep awake hacks. Not good.

VVlad Lykhonis Hi, any decent approach or documentation how to make sure or what guarantees a D...

L

Larry•10/19/25, 7:41 PM

It shouldn't hibernate when you are awaiting external fetch (what I assume you mean by "IO"). The limit on CPU usage defaults to 30 seconds but that clock doesn't run when you are only waiting on an external fetch. Also, it can be bumped up to 5 minutes.

1

1984 Ford Laser•10/20/25, 5:40 AM

I have a bunch of DO namespaces I want to convert from KV to SQL backend, is the official migration process coming soon or should I just create new namespaces and migrate data?

LLarry It shouldn't hibernate when you are awaiting external fetch (what I assume you m...

V

Vlad Lykhonis•10/20/25, 6:51 AM

Clock time you are referring to is worker cpu time limit?

11984 Ford Laser I have a bunch of DO namespaces I want to convert from KV to SQL backend, is the...

G

gruntlord6•10/20/25, 6:55 AM

you finally making the jump?

Ggruntlord6 you finally making the jump?

1

1984 Ford Laser•10/20/25, 6:57 AM

Yeah I'm in quiet season at work so I finally have time to dedicate to re-architecting everything

VVlad Lykhonis Clock time you are referring to is worker cpu time limit?

L

Lulu•10/20/25, 7:23 AM

i believe so

11984 Ford Laser I have a bunch of DO namespaces I want to convert from KV to SQL backend, is the...

L

lambrospetrouOP•10/20/25, 7:40 AM

There isn't an ETA yet, so if you need it now, I suggest doing the migration of the data yourself for now.

Llambrospetrou There isn't an ETA yet, so if you need it now, I suggest doing the migration of ...

1

1984 Ford Laser•10/20/25, 7:54 AM

No worries appreciate the clarity. I'll use it as an opportunity to rewrite everything while I'm at it, there's been plenty of changes I can take advantage of since I first built it all

VVlad Lykhonis Clock time you are referring to is worker cpu time limit?

L

Larry•10/20/25, 12:54 PM

I probably shouldn't have used the word "clock". It's confusing. DOs are billed on wall clock time. However, their run length limits are CPU clock time which is an order of magnitude or two more generous when you have external fetches involved. It wouldn't surprise me if it were able to wait on a fetch for 20 minutes. You'll pay for the DO the whole time, but it would still use less than 30 seconds of CPU.

1

1984 Ford Laser•10/21/25, 12:51 AM

If I delete a DO's storage, let it evict then request the same instance, will it always spawn in the same colo? I've gotten an instance in Perth which I'd really love to move closer to home

P

PhoenixSpace•10/21/25, 1:00 AM

If it's being spawned off of a request, it's usually pretty sticky from my experience, but if you specify a location hint instead I've had more success with it sometimes moving to a different datacenter. Not quite sure what the spawn algorithm is because it's seemingly slightly different each time I try.

For what it's worth, when I want a DO instance near a specific point, this is pretty inefficient but I just have a worker spawn and destroy DO instances with a region hint and with slightly different names then returns the name/id of the one in the POP I want

P

PhoenixSpace•10/21/25, 1:01 AM

This is in ENAM though, so I don't know how it is in other regions

PPhoenixSpace If it's being spawned off of a request, it's usually pretty sticky from my exper...

1

1984 Ford Laser•10/21/25, 1:02 AM

The locations I wanna use are within the same location hint, the routing just seems to really suck in this case (going from side of Australia to the other can be awful in terms of routing). I also don't really wanna have to stray away from the current name I am using for this instance

11984 Ford Laser The locations I wanna use are within the same location hint, the routing just se...

P

PhoenixSpace•10/21/25, 1:02 AM

Honestly, I'd just spin a quick test worker to spin and destroy a DO like 10 times with the same name with a set location hint. YMMV but usually thats enough to get a couple of different POPs. If that works, then just do that again with the DO class and name you want until it's in the right region then use it

PPhoenixSpace Honestly, I'd just spin a quick test worker to spin and destroy a DO like 10 tim...

1

1984 Ford Laser•10/21/25, 1:03 AM

I like it thank you

P

PhoenixSpace•10/21/25, 1:03 AM

np and please let me know how it goes. I haven't experimented with coercing DOs to specific POPs outside of ENAM/WNAM and would love to know if that hack works elsewhere lol

P

PhoenixSpace•10/21/25, 1:04 AM

My old trick was to spin a lambda instance in a nearby AWS center and hit the endpoint...

PPhoenixSpace np and please let me know how it goes. I haven't experimented with coercing DOs ...

1

1984 Ford Laser•10/21/25, 1:05 AM

Its never been a problem before, normally get them always in Melbourne which is close to home. There's only a 33% chance a DO will spawn in Perth via Melb instead of Sydney so I just got unlucky with this one. I will test out hitting the same instance and see how I go

11984 Ford Laser Its never been a problem before, normally get them always in Melbourne which is ...

P

PhoenixSpace•10/21/25, 1:07 AM

That makes sense. I'm working on a small tool that I'll need to put small DOs in very specific areas (one of which is in Australia) so I've been playing around more and more with forcing the DO placement algo where I want lol. I kinda wish CF could just let me specify the IATA code of where I want it, but I'm guessing there are architecture limitations there

1

1984 Ford Laser•10/21/25, 1:09 AM

So to confuse myself more, I just requested a new instance (first one was named '2025', this one is '2026') and it ended up in the same colo but with far better response times when hot?? Def need to test this out more

1

1984 Ford Laser•10/21/25, 1:09 AM

These instances are also entirely fresh with no data stored beyond the runtime-abstracted stuff

11984 Ford Laser If I delete a DO's storage, let it evict then request the same instance, will it...

I

Isaac McFadyen•10/21/25, 1:10 AM

As far as I remember, yes.

1

1984 Ford Laser•10/21/25, 1:10 AM

2025 gives me around 350ms when hot, 2026 gives me around 150ms which is not insignificant. Both in Perth