https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • y
    yeap guys, this issue only affects my IP, totally weird.
  • y
    the weirdest part is that, it only happens in Portugal - when I use VPN and go another location, it works. but all Portugal IPs in ProtonVPN, it returns same error
  • h
    Depending on what your Worker is doing, it might be an edge case to do with your colo(or something else), that causes an infinite loop. If you are able to give us some insight into what your code is doing(or a repo if you got one), then we might be able to help you.
  • y
    actually nothing, ordinary use of Zaraz + Cloudflare Pages - and not having any custom Workers, just using CF services with Workers
  • h
    Just a full static site with Zaraz, is that what you mean?
  • y
    yes, it is
  • h
    Hm…
  • h
    I’ll try to see if there is something I can do…
  • y
    To me, it appears that the problem is fixed. However, if the continuous ban persists in Portugal, then the issue may recur. In such a case, the problem will likely be resolved automatically in due time.
  • y
    thanks a lot for your close interest 🙏🏽 don't forget to check from Portugal based IP
  • h
    Yup, I see it borks in Lisboa
  • has anyone managed to get itty router v4
    m
    has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for 
    Request
    and 
    Response
    • 1
    • 1
  • e
    Has anyone managed to connect to redis using the new connect() api?
  • i
    Hi guys, what is the best for simply "counting requests per user", I am have a hard time on the economics because each time a user does something a write request has to be made even just for logging, the cheapest write request is on durable objects but it still costs 1$/1M
  • z
    Could #981314061268578304 work for your usecase?
  • z
    Otherwise, Durable Objects are the only thing that CF had that is really meant for strongly consistent counting
  • i
    It indeed does help, I am just worried because it is on beta and no pricing is available
  • i
    Thanks tho
  • z
    That's very understandable. There was some discussion in that channel about how pricing might work but AFAIK nothing is firm on that yet
  • i
    i am not sure if I should bet on it tbh, if such a product exists for the purpose of usage-based-billing (this is what says in the docs for one of the usages apparently), it should have a much lower price if we compare it to existing storage options
  • i
    But then people may abuse it
  • b
    are there already type declarations for the TCP socket api?
  • k
    there should be
  • k
    not sure why there hasn't been a release
  • k

    https://cdn.discordapp.com/attachments/779390076219686943/1109871135618777239/image.png▾

  • k
    it's under the alpha tag for whatever reason
  • k
    Copy code
    ts
declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}
  • m
    Any reason why when upgrading to Wrangler 3 and using the latest 
    compatibility_date
    why creating new Request objects would result in an empty object? Using module syntax, trying to create any new requests from within a module results in 
    {}
    when outputting it to console even with 
    console.log(JSON.stringify(req))
    ... bit stumped as this was working just fine before I tried migrating things to Wrangler v3 and updated my 
    compatibility_date
    ... any ideas? This is being done to create new Requests with custom cookies attached to pull information from an external website.
  • s
    You can't stringify requests
  • s
    Except on a really old compat version
1...248524862487...2509Latest