They are stored forever or until deleted

I asked about pricing for storage and it's below

Ohhh i see the table now

https://developers.cloudflare.com/workers/platform/pricing/#durable-objects is my answer

so cool, wrangler asks me to navigate to

https://dash.cloudflare.com/$id/workers/overview?enable-durable-objects

, except that doesn't bring up any modal or anything

what's the correct url?

Are you on the paid version of Workers? I believe that's all that's necessary these days: https://developers.cloudflare.com/workers/learning/using-durable-objects/#using-durable-objects-1

hey, does anyone know why I get

Unhandled Promise Rejection: TypeError: this.state.blockConcurrencyWhile is not a function

when using

itty-durable

? I thought I should be able to access it:

oh yeah this is being called from within an alarm. maybe that is the problem

Hi, we would like to use durable objects in our project, after deploying i dont see durable objects in worker. toml file:

[durable_objects]
bindings = [{name = "COUNTER1", class_name = "Counter"}]

durable object reference:

let id = env.COUNTER1.idFromName(requestIp);
let obj = env.COUNTER1.get(id);
let resp = await obj.fetch(request.url);
let count = parseInt(await resp.text())

Durable object class:

export class Counter {
  state: any;
  constructor(state:any) {
    this.state = state;
  }
  async fetch(request:any) {
    // Apply requested action.
    let url = new URL(request.url);
    let value = await this.state.storage.get("value") || 0;
    ++value;
    await this.state.storage.put("value", value);
    return new Response(value);
  }
}

binding.ts:

COUNTER1: DurableObjectNamespace;

Error after deploying using wrangler publish: ✘ [ERROR] TypeError: Cannot read properties of undefined (reading 'idFromName') can someone help here?

Does it show the DO binding when you run publish?

no, DO binding also not shown

You're missing a

migrations

entry that you need when you define, rename or remove a DO class Add this to the end of wrangler.toml:

toml
[[migrations]]
tag = ''
new_classes = ['Counter']

after adding [[migrations]], i see binding created but still same error when worker runs.

✘ [ERROR]   TypeError: Cannot read properties of undefined (reading 'idFromName')

hmm, could you share more of your worker code?

public static async processRequest(request: Request, env: Bindings): Promise<Response> {
        const requestIp:string | null  = request.headers.get('CF-Connecting-IP');
        const requestUrl:string = request.url;
        
        //const list = await env.test_kv_binding.list({});
        if(requestIp && requestUrl.includes("test url")) {
            if(requestIp) {
                let id = env.COUNTER1.idFromName(requestIp); //facing error here
                let obj = env.COUNTER1.get(id);
                let resp = await obj.fetch(request.url);
                let count = parseInt(await resp.text())
                console.log('count : ', count);
            }
}

binding.ts:

interface Bindings {
    COUNTER1: DurableObjectNamespace;
}

index.ts

import { RequestDomain } from './request/request.domain';

export async function handleRequest(request: Request, env: Bindings) {
  return await RequestDomain.processRequest(request, env);
}

export class Counter {
  state: any;
  constructor(state:any) {
    this.state = state;
  }

  async fetch(request:any) {
    let url = new URL(request.url);
    let value = await this.state.storage.get("value") || 0;
    ++value;
    await this.state.storage.put("value", value);

    return new Response(value);
  }
}

const worker: ExportedHandler<Bindings> = { fetch: handleRequest };

export default worker;

hmm, I didn't see anything right away, let me check something

ok

Your worker code seems fine, are you using environments by any chance? (That would be

--environment prod

, for example, when deploying)

yes wrangler publish -e DEV

and do you have the

durable_objects.bindings = []

under the env definition? Bindings don't get inherited

yes my env file below name = "cf_interceptor_dev" main = "dist/index.mjs" account_id = "xx" workers_dev = true compatibility_date = "2022-05-28" compatibility_flags = [] [env.DEV] name = "cf_interceptor_dev" workers_dev = false kv_namespaces = [ { binding = "test_kv_binding", id = "xx" } ] [durable_objects] bindings = [{name = "COUNTER1", class_name = "Counter1"}] routes = [] [env.DEV.vars] WEB_APP_DOMAIN='test' [build] command = "node build.js" [[migrations]] tag = '' new_classes = ['Counter1']

yup, so if you define it as [durable_objects], that's no longer under [env.DEV], but it's own thing

so you can either do [env.DEV.durable_objects], just like you have with vars, or do

durable_objects.bindings

instead of

bindings

my bad, it works great now. thanks a lot for the help @Dani Foldi

Glad you got it working, happy to help!

are durable object value size limits enforced when developing locally? either they are not or I don't understand the size limit

they should be afaik

you can always deploy and see if it doesnt allow the same as local 🤷

js
console.log("SIZE", JSON.stringify(await queueStub.toJSON()).length);

output: SIZE 134275 shouldn't be possible, right? that is using itty-durable which stores the whole value in a single "field"