Yep! That's me

PPhatso Yep! That's me

E

Erisa•7/3/23, 9:30 AM

Hey

do you have a link to the message you were referring to, so I can understand the context?

D

docy•7/3/23, 3:12 PM

is there any way to get keys in bulk? googled but couldn't find anything

something like this:

env.NAMESPACE.get(['foo', 'bar', 'bang'])

env.NAMESPACE.get(['foo', 'bar', 'bang'])

env.NAMESPACE.get(['foo', 'bar', 'bang'])

env.NAMESPACE.get(['foo', 'bar', 'bang'])

K

kian•7/3/23, 3:13 PM

Not with the Worker bindings, no

D

docy•7/3/23, 3:13 PM

why is it available over http api but not worker bindings?

K

kian•7/3/23, 3:13 PM

I don't see it in the API either

K

kian•7/3/23, 3:14 PM

There's bulk writes and deletes, but no gets.

D

docy•7/3/23, 3:14 PM

oh yeah i misread

D

docy•7/3/23, 3:14 PM

that's weird

D

docy•7/3/23, 3:14 PM

wonder why

E

eg_scl•7/3/23, 5:26 PM

I'm struggling with using kv, are there any good whole project examples. I see in the docs there is a tutorial for rust, but not ES. I'm just getting null when I call env.NS.get('whatever') and I'm sure it's got to be a setting so I'm looking for a whole working project to compare too. Thanks.

K

kian•7/3/23, 5:51 PM

https://developers.cloudflare.com/workers/runtime-apis/kv/#reading-key-value-pairs

```
get
```
get
```
get
```
get
will be
```
null
```
```
null
```
if that key doesn't exist.

E

eg_scl•7/3/23, 5:58 PM

Thanks @kian - thing is, I can get the correct value from the command line "wrangler kv:key get --namespace-id=### "{key}" but it just doesn't in the worker.js. My binding has the same preview_id as I used in the commandline call. so I'll keep trying.

K

kian•7/3/23, 6:04 PM

Is it a published Worker?

K

kian•7/3/23, 6:04 PM

Wrangler dev defaults to local development, so it has no access to your real KV namespace.

E

eg_scl•7/3/23, 6:40 PM

@Kian oh. I did not see that mentioned in the docs. I'm using local. So is there a local kv to setup and use?

MMallissin Is there a way to get the last modified date of a key or do I need to add it int...

P

PhatsoOP•7/3/23, 8:34 PM

Metadata only

Eeg_scl @Kian oh. I did not see that mentioned in the docs. I'm using local. So is there...

E

eg_scl•7/3/23, 11:42 PM

I did get it to work a bit but I still don't understand. I deployed, my wrangler.toml file has workers_dev=true yet the key value doesn't come from the namespace specified by preview_id

Eeg_scl I did get it to work a bit but I still don't understand. I deployed, my wrangler...

E

eg_scl•7/4/23, 2:17 AM

SOLVED: I just needed to add --remote to the end of 'wrangler dev --remote' now I can read KV from localhost.

M

marina.lipeck•7/4/23, 1:56 PM

Hey, this announcement - https://blog.cloudflare.com/faster-workers-kv-architecture/#:~:text=If%20these%20sound%20like%20the%20killer%20features%20you%20need%2C%20please%20reach%20out%20to%20us%20if%20you%E2%80%99re%20interested%20in%20trying%20them%20out about new exiting features says that one can reach out and try out them earlier then ga - how can I do it?

The Cloudflare Blog

Workers KV is faster than ever with a new architecture

With the new architecture powering Workers KV our service will become faster and more scalable than ever. We have significantly reduced cold read probability, and enabled KV to serve over a trillion requests a month

C

Cyb3r-Jak3•7/5/23, 12:12 PM

What do you mean by updating KV? If you have an existing worker that has an existing KV binding then it should continue to function. With the maintenance, there might be issues with creating a new worker, kv namespace, or binding the namespace to a worker

Ddam6pl Managing KV values in existing namespace in existing Worker binding 🙂

C

Cyb3r-Jak3•7/5/23, 12:19 PM

My understanding is those operations should not be affected

0

0x33•7/7/23, 12:31 AM

I'm trying to write something to a KV and it stays unaffected. :/

await env.HEADERS.put(uuid, packedHeaders, { expirationTtl: 60 * 60 * 24 * 7 });

await env.HEADERS.put(uuid, packedHeaders, { expirationTtl: 60 * 60 * 24 * 7 });

await env.HEADERS.put(uuid, packedHeaders, { expirationTtl: 60 * 60 * 24 * 7 });

await env.HEADERS.put(uuid, packedHeaders, { expirationTtl: 60 * 60 * 24 * 7 });

I tried on my localhost and in deployed production. Wrangler (3.1.2) does not issue any error/warning. What can be the cause?

0

0x33•7/7/23, 12:34 AM

Am I using outdated

toml

toml

toml

toml?

[[kv_namespaces]]
binding = "HEADERS"
id = "xxx"
preview_id = "xxx"

[[kv_namespaces]]
binding = "HEADERS"
id = "xxx"
preview_id = "xxx"

[[kv_namespaces]]
binding = "HEADERS"
id = "xxx"
preview_id = "xxx"

[[kv_namespaces]]
binding = "HEADERS"
id = "xxx"
preview_id = "xxx"

0

0x33•7/7/23, 12:37 AM

Just tried

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

kv_namespaces = [
  { binding = "<MY_NAMESPACE>", id = "<KV_ID>" }
]

Doesn't work..

0

0x33•7/7/23, 1:00 AM

I inserted some keys and values via the dashboard and

await env.HEADERS.get(..)

await env.HEADERS.get(..)

await env.HEADERS.get(..)

await env.HEADERS.get(..) returns

null

null

for them

C

Chaika•7/7/23, 1:01 AM

If you're using wrangler 3.x, the default wrangler dev is local/all local data, have to use wrangler dev --remote to access real KV namespaces/data

0

0x33•7/7/23, 1:07 AM

That works with the preview KV namespace! Thanks! How do I make it work for production deployment?

0

0x33•7/7/23, 1:10 AM

I

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy

npx wrangler deploy ed the same code. The binding IDs are correct and nothing shows up in the KV. The worker gets hit 155k/24h

C

Chaika•7/7/23, 1:12 AM

Is your kv namespace id and preview id the same? dev --remote will use preview_id, and deployed worker will use normal id, might be the cause of some confusion.

0

0x33•7/7/23, 1:15 AM

These are different IDs. I understand that preview has a different purpose to production. There was a warning about that when I tried to run

npx wrangler dev

npx wrangler dev

npx wrangler dev

npx wrangler dev too.

binding = "HEADERS"
id = "659461f0c2c446b..."
preview_id = "65ee1a3b420c4b..."

binding = "HEADERS"
id = "659461f0c2c446b..."
preview_id = "65ee1a3b420c4b..."

binding = "HEADERS"
id = "659461f0c2c446b..."
preview_id = "65ee1a3b420c4b..."

binding = "HEADERS"
id = "659461f0c2c446b..."
preview_id = "65ee1a3b420c4b..."

0

0x33•7/7/23, 1:18 AM

I double checked the IDs and just redeployed the same code. No errors from workers

C

Chaika•7/7/23, 1:18 AM

Right, my line of thinking was "are you checking the right one"? If your worker simply puts that on every request, you should be able to see those values in the dashboard. Can you see them there? If so, it is just the worker itself not being able to get them later, or something else?

0

0x33•7/7/23, 1:21 AM

5 records appeared in the KV but the strange thing is that it only contains my 5

curl

curl

requests I made after the deploy. Is there a delay in the global worker deployment or is the KV localised?

0

0x33•7/7/23, 1:21 AM

0

0x33•7/7/23, 1:22 AM

0

0x33•7/7/23, 1:23 AM

C

Chaika•7/7/23, 1:24 AM

KV is global, that kinda sounds like to me you're looking at the preview and not the production namespace, or you have something with your code that is preventing writes. Workers are pretty quick to deploy globally, maybe 10-15s

0

0x33•7/7/23, 1:26 AM

  async fetch(request, env, ctx) {
// ... snip ...
    await env.HEADERS.put(uuid, data, { expirationTtl: 60 * 60 * 24 * 7 });
// ... snip ...

  async fetch(request, env, ctx) {
// ... snip ...
    await env.HEADERS.put(uuid, data, { expirationTtl: 60 * 60 * 24 * 7 });
// ... snip ...

  async fetch(request, env, ctx) {
// ... snip ...
    await env.HEADERS.put(uuid, data, { expirationTtl: 60 * 60 * 24 * 7 });
// ... snip ...

  async fetch(request, env, ctx) {
// ... snip ...
    await env.HEADERS.put(uuid, data, { expirationTtl: 60 * 60 * 24 * 7 });
// ... snip ...

This is the worker code. It uses

export default {

export default {

export default {

export default { syntax. Every request should hit it.

0

0x33•7/7/23, 1:27 AM

Hmm...

0

0x33•7/7/23, 1:27 AM

Is it safe to post namespace ids here?

0

0x33•7/7/23, 1:28 AM

0

0x33•7/7/23, 1:29 AM

I'm cetain that this is the same

id

id

id

id as in

[[kv_namespaces]]

[[kv_namespaces]]

[[kv_namespaces]]

[[kv_namespaces]]

id =

id =

id =

id =

0

0x33•7/7/23, 1:29 AM

Maybe I'm doing something really silly.

0

0x33•7/7/23, 1:32 AM

Could you tell if this might be the culprit? I'm using a custom domain "without custom domain". I created route and DNS record manually so the requests are possibly routed to the old worker instances and the new code is never executed. I've never actually used the

Connect your Worker to a custom domain.

Connect your Worker to a custom domain.

Connect your Worker to a custom domain.

Connect your Worker to a custom domain. panel.

0

0x33•7/7/23, 1:33 AM

When I ran

curl

curl

I used

*.workers.dev

*.workers.dev

*.workers.dev

*.workers.dev which contains the most fresh deployment.

0

0x33•7/7/23, 1:39 AM

Yes. That was it!

Similar Threads

Similar Threads

Similar Threads