https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • s
    (curious, planning on using for my Worker)
  • c
    You can use it else where but it is free from workers
  • k
    So I added the custom domain but it didn't add an "A" record type. Do I need to add a route under trigger also for the domain?
  • k
    It just added a record type of "Worker"
  • s
    Gotcha, so if someone tried to use the API from a non-Worker service it wouldn't work without them paying. Aka there's some IP/infra based verification?
  • c
    No the custom domain is the trigger
  • k
    I get NXDOMAN unfort
  • k
    My zone is managed in CF
  • c
    Yeah. Don't know how it works for other service but it only works with workers it only works on deployed workers not local or quick edit
  • s
    Ah gotcha, so I'll need to deploy my code to test it thank you!
  • c
    Never used it but I think 
    wrangler dev
    should work but not 
    wrangler dev --local
  • s
    Makes sense, appreciate the help!
  • s
    I'm using slshx for Discord Slash Commands (using Miniflare) and I'm randomly getting:
    Copy code
    [mf:err] POST /: NotSupportedError: Unrecognized name.
    When I try to upgrade miniflare + wrangler I get:
    Copy code
    [mf:err] POST /: TypeError: Failed to parse URL from [object Object]
    I didn't do anything so I have no idea why this happened. A quick search shows this thread from last year: https://github.com/cloudflare/miniflare/issues/144 But it should've been patched as far as I can tell with 2.1.0 🤔 Any ideas?
  • a
    Is there a guarantee of the KV propagation time in the same zone, or is it still 60 seconds? In other words, can I expect that if a worker invoked by a user stores something in KV, if the same user asks for the value back it wouldn't be a full 60 seconds until he gets the correct result?
  • u
    KV isn't delayed by 60s because of propagation it's delayed because it caches values on read for 60s
  • u
  • a
    So is it basically impossible to build applications where the user needs to be able to modify data and use it on workers
  • u
    It's fully possible
  • u
    In the same colo a write will update it's cache which means it's instantly available (for the most part)
  • u
    But also you can use multiple key value pairings instead of one huge blob for everything
  • b
    If you need a guaranteed read, you can use a durable object to manage the write and reads.
  • c
  • c
    Look at the version
  • c
    I have removed cache multiple times from dashboard and also with:
    Copy code
    js
await this.cache.delete("https://api.rabbitserverlist.com?key=" + key);
  • c
    It's getting less and less noticable over time but even after half an hour I'm still sometimes seeing 1.19.4 instead of 1.19.3
  • b
    The first set of Node.js APIs have officially landed in Cloudflare Workers — 
    AsyncLocalStorage
    , 
    EventEmitter
    , 
    Buffer
    , 
    assert
    , and 
    util
    . No polyfills required — these are the real deal. **Blog post**: https://blog.cloudflare.com/workers-node-js-asynclocalstorage/ **Docs**: https://developers.cloudflare.com/workers/runtime-apis/nodejs/ You can try these out in your Worker today, by enabling the 
    nodejs_compat
    compatibility flag in your 
    wrangler.toml
    We'd love to hear what you think! cc @User
  • c
    Does 
    await caches.default.delete(key)
    globally remove data from all servers / data centers? Probably not right?
  • k
    Nope, just for that single colo
  • c
    So the "best" way to remove item from cache globally ("instantly") is to not use cache at all or to set it something small like a minute?
  • e
    or use the CF API to purge
1...235523562357...2509Latest