The only other thought I have is that we do have 1 slight change. We currently don’t upsert on put i

Bbeelzabub The only other thought I have is that we do have 1 slight change. We currently d...

B

beelzabubOP•5/24/23, 1:59 PM

export default {
  async fetch(request, env, ctx) {
    if (request.headers.get('authorization') !== 'abc') {
      return new Response('not authorized', { status: 401 })
    }
    try {
      const key = "registrationChallenge/bob4@foo.bar"
      const value = Math.random().toString()
      const firstGet = await env.KV.get(key) ?? "<null>"
      await env.KV.put(key, value)
      const secondGet = await env.KV.get(key) ?? "<null>"
      return new Response(JSON.stringify({
        key,
        firstGet,
        updated: value,
        secondGet,
      }, undefined, 2));
    } catch (e) {
      return new Response(e.stack, { status: 500 });
    }
  },
};

export default {
  async fetch(request, env, ctx) {
    if (request.headers.get('authorization') !== 'abc') {
      return new Response('not authorized', { status: 401 })
    }
    try {
      const key = "registrationChallenge/bob4@foo.bar"
      const value = Math.random().toString()
      const firstGet = await env.KV.get(key) ?? "<null>"
      await env.KV.put(key, value)
      const secondGet = await env.KV.get(key) ?? "<null>"
      return new Response(JSON.stringify({
        key,
        firstGet,
        updated: value,
        secondGet,
      }, undefined, 2));
    } catch (e) {
      return new Response(e.stack, { status: 500 });
    }
  },
};

export default {
  async fetch(request, env, ctx) {
    if (request.headers.get('authorization') !== 'abc') {
      return new Response('not authorized', { status: 401 })
    }
    try {
      const key = "registrationChallenge/bob4@foo.bar"
      const value = Math.random().toString()
      const firstGet = await env.KV.get(key) ?? "<null>"
      await env.KV.put(key, value)
      const secondGet = await env.KV.get(key) ?? "<null>"
      return new Response(JSON.stringify({
        key,
        firstGet,
        updated: value,
        secondGet,
      }, undefined, 2));
    } catch (e) {
      return new Response(e.stack, { status: 500 });
    }
  },
};

export default {
  async fetch(request, env, ctx) {
    if (request.headers.get('authorization') !== 'abc') {
      return new Response('not authorized', { status: 401 })
    }
    try {
      const key = "registrationChallenge/bob4@foo.bar"
      const value = Math.random().toString()
      const firstGet = await env.KV.get(key) ?? "<null>"
      await env.KV.put(key, value)
      const secondGet = await env.KV.get(key) ?? "<null>"
      return new Response(JSON.stringify({
        key,
        firstGet,
        updated: value,
        secondGet,
      }, undefined, 2));
    } catch (e) {
      return new Response(e.stack, { status: 500 });
    }
  },
};

This prints for example:

{
  "key": "registrationChallenge/bob4@foo.bar",
  "firstGet": "<null>",
  "updated": "0.6567038844336677",
  "secondGet": "0.6567038844336677"
}

{
  "key": "registrationChallenge/bob4@foo.bar",
  "firstGet": "<null>",
  "updated": "0.6567038844336677",
  "secondGet": "0.6567038844336677"
}

{
  "key": "registrationChallenge/bob4@foo.bar",
  "firstGet": "<null>",
  "updated": "0.6567038844336677",
  "secondGet": "0.6567038844336677"
}

{
  "key": "registrationChallenge/bob4@foo.bar",
  "firstGet": "<null>",
  "updated": "0.6567038844336677",
  "secondGet": "0.6567038844336677"
}

B

beelzabubOP•5/24/23, 2:01 PM

Adding an

expirationTtl

expirationTtl

has no effect. We did start the rollout of the new KV caching infrastructure on Monday which might explain the observed difference but I don't see anything in Sentry, our logging, nor can I reproduce what you're observing...

B

beelzabubOP•5/24/23, 2:13 PM

The more complex key works too:

{
  "key": "registrationChallenge/helloworld+1////22///%2f+++...\\<<<>/@test.com:443//",
  "firstGet": "<null>",
  "updated": "0.41442319206749634",
  "secondGet": "0.41442319206749634"
}

{
  "key": "registrationChallenge/helloworld+1////22///%2f+++...\\<<<>/@test.com:443//",
  "firstGet": "<null>",
  "updated": "0.41442319206749634",
  "secondGet": "0.41442319206749634"
}

{
  "key": "registrationChallenge/helloworld+1////22///%2f+++...\\<<<>/@test.com:443//",
  "firstGet": "<null>",
  "updated": "0.41442319206749634",
  "secondGet": "0.41442319206749634"
}

{
  "key": "registrationChallenge/helloworld+1////22///%2f+++...\\<<<>/@test.com:443//",
  "firstGet": "<null>",
  "updated": "0.41442319206749634",
  "secondGet": "0.41442319206749634"
}

Bbeelzabub The more complex key works too: ``` { "key": "registrationChallenge/helloworld...

A

asp•5/24/23, 2:40 PM

Ha, that's my key! I exaggerated the special characters to see if there was an URL encoding issue

A

asp•5/24/23, 2:43 PM

Was testing with both KV1 and KV2 to see if that made any difference.

Aasp Was testing with both KV1 and KV2 to see if that made any difference.

B

beelzabubOP•5/24/23, 2:44 PM

I know :). We did actually have a URL encoding issue before but that would manifest as uploads failing as well.

Original message was deleted

B

beelzabubOP•5/24/23, 4:29 PM

That's currently the best mechanism if that works for you.

Original message was deleted

A

asp•5/24/23, 5:14 PM

Beware expiration is from when you write. It does not refresh on read. So a key can be read a lot and still expire once the TTL is over.

AAnna | DevMiner Small bug report: the name of a KV namespace on the website uses default input s...

A

asp•5/25/23, 9:27 AM

Could you please share a screenshot of what you mean by this?

B

beelzabubOP•5/25/23, 2:07 PM

Are you saying because it's got a black background in the dark theme? Or because it's non-obvious that it's editable?

B

b-fuze (Mike32)•5/27/23, 2:56 AM

Is there a way to list keys from KV in reverse?

B

b-fuze (Mike32)•5/27/23, 2:57 AM

As far as I understand it, KV orders keys in ascending order lexicographically righ?

B

b-fuze (Mike32)•5/27/23, 2:57 AM

Is there a way to get the "top 10" keys or something?

Bb-fuze (Mike32)Is there a way to list keys from KV in reverse?

U

Unsmart•5/27/23, 4:30 AM

Not currently sadly sadge

B

b-fuze (Mike32)•5/27/23, 4:31 AM

Ah, okay. I'll have to store my keys in reverse then

U

Unsmart•5/27/23, 4:31 AM

#durable-objects do support reverse sort and you could add cache api on top of DOs which would make it somewhat close to KV

B

b-fuze (Mike32)•5/27/23, 4:31 AM

Thanks

B

b-fuze (Mike32)•5/27/23, 4:49 PM

So I have a problem, I write data to KV (via a CF worker), then in another request (to a CF worker) I

list

list

keys then run

get

get

get

get on those keys. My problem is that

get

get

get

get returns

null

null

if I

get

get

get

get those keys too quickly (after the write request)... What is the proper solution here? I'm thinking of writing a

while

while

while

while loop that keeps

get

get

get

geting those keys until KV returns something other than

null

null

?

J

James•5/27/23, 5:47 PM

This is really by design with the way that KV's eventual consistency model works: https://developers.cloudflare.com/workers/learning/how-kv-works/

J

James•5/27/23, 5:48 PM

You could do a

while

while

while

while loop, but it really sounds like you want more durable storage, so something like Durable Objects would likely be better suited: https://developers.cloudflare.com/workers/learning/using-durable-objects/

B

b-fuze (Mike32)•5/27/23, 6:17 PM

Thanks!

U

Unsmart•5/27/23, 7:35 PM

That is interesting that the list shows it though on first get it shouldn’t be cached. Unless you tried to do a get before the list then get

B

b-fuze (Mike32)•5/27/23, 10:16 PM

Yeah, Idk what's going on

B

b-fuze (Mike32)•5/27/23, 10:17 PM

What I've decided to do was store the creation date in the key metadata, and wait 60 seconds after it's created (if I'm trying to get the value before that time)

B

b-fuze (Mike32)•5/27/23, 10:18 PM

I tried using lower values like 30 seconds, etc, but I was still getting nulls. It seems like 60 seconds is how long I should wait before I can confidently not get a null value

W

Walshy•5/29/23, 11:05 PM

Consistently as in like 100% of the time or?

W

Walshy•5/29/23, 11:07 PM

That's fun.. all keys?
Is that namespace enrolled into kv2?

W

Walshy•5/29/23, 11:08 PM

Interesting - @robsutter @beelzabub if either of you are around

W

Walshy•5/29/23, 11:15 PM

Sent a message internally

Eeidam ok it looks like same keys all over again

W

Walshy•5/29/23, 11:23 PM

Can you send some of the key names?

U

Unsmart•5/30/23, 2:18 AM

You wouldnt store JWTs so im confused what you would be using KV for in that sense