if code inside a DO crashes

does the whole DO restart and loses its local state?

how does one use KV for workers inside a DO

i keep getting its not defined

i think i attached the KV using the web gui not wrangler

could it be bugged?

i cant detach it

is there any chance to get metadata on durable object storage same to Worker KV?

that metadata makes it really easy to paginate with filters

not only easy, but possible

some more complex filters are impossible to list with the current way DOs work. because you cannot properly place start

a way to get only the keys would be nice too

the problem is kinda ths

so if I wanna paginate via list

with limit of 100

each read will readback full object, thats 100 reads for 1 list?

vs the KV worker storage, list had its own cost

i guess I am asking if this function will cost a fortune

javascript
  async get_jobs_by_filter({queued, in_progress, finished, failed}, page, limit, acc, offset) {
    offset = offset || 0
    acc = acc || []
    var objects = await this.storage.list({start: offset, limit: 1000})
    var jobs = objects.values.filter(job=> {
        if (queued && job.status == "queued")
          return true;
        if (in_progress && job.status == "in_progress")
          return true;
        if (finished && job.status == "done")
          return true;
        if (failed && job.status == "error")
          return true;
        return false
    })
    acc = acc.concat(jobs);

    //abort early
    var skip = page*limit
    if (acc.length >= skip+limit) {
        return acc.slice(skip, limit)
    }

    if (objects.size == 1000) {
        return get_jobs_by_filter({queued, in_progress, finished, failed}, page, limit, acc, offset + 1000)
    } else {
        return acc.slice(skip, limit)
    }
  }

size of key 32bytes size of value around 8kb

on KV Worker i just set the 4 boolean filters as metadata

i dont want to use KV worker with DO because its inconsistent, soemtimes KVWorker updates instantly, other time takes 15 seconds

Thanks, that did the trick!

@User having some trouble getting the sites template to work with type=javascript and upload_format=modules:

__STATIC_CONTENT is not defined

. kv-asset-handler seems to depend on some globals that are available in the webpack environment but not javascript + modules format for some reason. is this something i can resolve on my own, or is there magic happening behind the scenes?

Ah looks like

__STATIC_CONTENT

is passed through the

env

argument for module workers

After updating kv-asset-handler to use

env

instead, I now get the error:

there is no KV namespace bound to the script

, so I think something behind the scenes may have to change.

env.__STATIC_CONTENT

is defined, but it's an empty object.

@User any plans to make it easily mockable for dev, or should I mock on top of itty durables?

Pretty sure I had this same issue a month or so ago as I am using the new module format for both worker and DO - I ended up having to make quite a few (workaround) changes to kv-asset-handler, including creating my own version of the manifest and passing that as an option to getAssetFromKV. Newer versions of wrangler may fix that issue somewhat.