DI get an error when using the kv_namesapces=[...]
could it be because of the extension I am using?
Name: Even Better TOML
Id: tamasfe.even-better-toml
Description: Fully-featured TOML support
Version: 0.19.2
Publisher: tamasfe
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml
could it be because of the extension I am using?
Name: Even Better TOML
Id: tamasfe.even-better-toml
Description: Fully-featured TOML support
Version: 0.19.2
Publisher: tamasfe
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml
Extension for Visual Studio Code - Fully-featured TOML support
HI'm using the same, no error with
Dhmm.. I wonder what's wrong with mine...
HCan you post the whole
wrangler.tomlI dont have nitro... I'll be sending it in parts
DDHI see the issue
Dthe rest are just literal comments.. so I guess it doesn't matter?
Hkv_namespace is under d1_databasesPlace it underneath
pages_build_output_dirDoh wow it did the trick!
Why? so does this mean that on the wrangler toml file the kv namespace should be declared above d1 database?
Why? so does this mean that on the wrangler toml file the kv namespace should be declared above d1 database?
HTOML Shenanigans. Basically, when you add a table declaration(
[placement]) or a table array declaration([[d1_databases]]), everything until the next declaration is assumed to be a part of that tableHThis is why I no longer use
toml for personal projectsDthat makes sense! Hmm how do we prevent that?
also, isn't wrangler.toml required in deploying apps in cloudflare?
also, isn't wrangler.toml required in deploying apps in cloudflare?
HI use
wrangler.json. It is supported for Workers, but not for Pages
NAny possible answer to why files in the KV store can be unfindable? could it be the caching or something else?
ZIf you make a request for a key that doesn't yet exist, the not found response will be cached for the same TTL as if it were found. Default 60 seconds iirc, but can be overridden
HNote here that it can be raised above 60 seconds, but not lowered
TFor the first time I got the message "Daily request limit exceeded for Cloudflare Workers"
This worker have an average (and pretty stable) of 250/350 writes every day, and I just checked on the dashboard without seeing anything strange. How should I best proceed?
Thank you!
This worker have an average (and pretty stable) of 250/350 writes every day, and I just checked on the dashboard without seeing anything strange. How should I best proceed?
Thank you!
NHi all, when I am using list method and cursor for pagination (https://developers.cloudflare.com/kv/api/list-keys/#list-method). What happens if I have 1 milion keys and when I get a page I trigger delete of that keys and then use cursor to go to the second page? Would cursor have an old list so it will continue serving correct pages even though that I am deleting keys in the background?
Cloudflare Docs
To list all the keys in your KV namespace, call the list() method of the KV binding on any KV namespace you have bound to your Worker code:
THey folks! We just shipped the new Analytics GraphQL API and Dashboard UI for Workers KV 
Now, you can get per-namespace analytics and more details such as cache status and latency information, and it's standardized on the same GraphQL API layer as other Cloudflare products.
Check it out in action (looks even better in person)!
https://developers.cloudflare.com/kv/platform/changelog/#2024-08-08
Now, you can get per-namespace analytics and more details such as cache status and latency information, and it's standardized on the same GraphQL API layer as other Cloudflare products. Dashboard UI: You can try this one directly from the dashboard, just go to one of your KV namespaces and see the new metrics UI.
GraphQL API: You can now get your KV analytics directly from the standard GraphQL API (sample queries and how to configure your requests here: https://developers.cloudflare.com/kv/observability/metrics-analytics/)
Check it out in action (looks even better in person)!
https://developers.cloudflare.com/kv/platform/changelog/#2024-08-08
N@thomasgauvin really awesome view and great information source. One thing that I noticed is that if KV is big it doesn't show KV count
MHeya—I assume probably not, but is there a way to tweak the usage limit email threshold? I'm getting daily "you have used 50% of the free tier!" emails... from a cron job that reliably uses just over half of the free tier allotment :D
M(er, wait... no, it doesn't, it uses like 1/3. seems like essentially a duplicate of this thread, I'll stay tuned on that)
M
EDoes KV have a feature for checking existing keys on write? By default it does not but is there a feature that can be turned on to enable such a thing?
HNo, and no
EI knew but I had to ask anyway. Can you clarify if I'm being paranoid then. I want to store magic tokens(that expire after an hour) and although I've gone to great lengths to make the token unique, there is always that statistically improbable chance that a duplicate token is created within that ttl window. I'm I crazy for trying to check for duplicates when the chance for that is as probable as the sun going out?
EIt also could just be the way I'm implementing the magic token system that invites uncertainties.
HYou could also just use DOs?
HThen have it fail the write if it already exists?
EForgive me, what is a DO?
HCloudflare Docs
Durable Objects provide a powerful API for coordinating multiple clients or users, each with private, transactional and strongly consistent storage attached.
EAh okay, so this is available through the transactional storage api?
HOr well, each DO has a separate KV Store
EThanks, I'll take a proper read through it.
TThis seems like an optimization for an extremely unlikely use case. How many keys do you plan on storing and is it anywhere near risking hash collision?
You could also reduce probably by making a read first, and writing it if it doesn't exist. It won't deterministically guarantee that you aren't overwriting, because it may have been written/propagated to KV since the read, but it wouldn't hurt in reducing chances of collision
If you need stronger unique guarantees, DO/D1 may be better options
You could also reduce probably by making a read first, and writing it if it doesn't exist. It won't deterministically guarantee that you aren't overwriting, because it may have been written/propagated to KV since the read, but it wouldn't hurt in reducing chances of collision
If you need stronger unique guarantees, DO/D1 may be better options
EMy plan is to reuse this authentication and session system whenever I can when making Sveltekit projects so I wanted to make something robust enough to handle a large number of users authenticating themselves frequently. I've considered reading before the writing but as you mentioned it only reduces the chances on top of an extra network call. D1 was the only real solution for me before learning about DO.
EAs for the use cases. I probably may never generate enough magic tokens to increase the odds of a duplication within a period of time as the size of the tokens is 64 chars generated by the crypto module. I think I just wanted a solution to a hypothetical problem.:NotLikeThis:
HMake a separate KV for every project and you should be fine
HIf you really want to avoid collision at all cost, then you can append a unix timestamp to the token
HIf you manage to generate two identical 64 char tokens within a single second you would probably be the luckiest human to have ever existed. Heck, even getting a single collision at all would make you the luckiest person of all time
HYou could also generate a UUID7 which has a granularity of up to 50 nanoseconds 
TYou should probably store your information in D1, then optimize with KV (ie once a user logs in, check hash against db hashed, but then store tokens in kv and use that for auth validation)
AWhy key-value data storage is so expensive comparing to other resources?
KV read price - $0.50/million
Durable objects (that sounds a lot more complex, "permanent" and expensive) - $0.15/million
D1 database - $0.001 / million rows reads
Why everything else, where I can store some data is cheaper? Isn't kv - a cheap, temporary, cache storage?
KV read price - $0.50/million
Durable objects (that sounds a lot more complex, "permanent" and expensive) - $0.15/million
D1 database - $0.001 / million rows reads
Why everything else, where I can store some data is cheaper? Isn't kv - a cheap, temporary, cache storage?
MCloudflare Docs
Workers KV is a data storage that allows you to store and retrieve data globally. With Workers KV, you can build dynamic and performant APIs and websites that support high read volumes with low latency.
TAnd to add on to Matt's response, each key-value pair in KV can handle a much higher throughput than individual rows in D1
AHmm, ok. Is KV the best tool to store and read some cache data? Like I have a complex worker function. During its work, I have to hit several 3rd party API. And I don't want to call them on every worker execution. I want to temporary cache data. On regular server I would use redis or a simple in-memory cache. What about worker? What should I use here? KV?
TYes, KV is the tool for this. there's cache api https://developers.cloudflare.com/workers/runtime-apis/cache/ but that is definitely an optimization and might get evicted from cache