https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • s
    I see no double crons there?
  • u
    pretty much all of them expect 17:00 17:01 triggered twice in a minute
  • u
    still triggering more often than it should even because its 2 minute cron interval
  • c
    Crons are kinda weird, when they stay at the same location, they stay at the same second (but otherwise no guarantee of second). Can see :09 and :55 being duplicate schedules
  • u
    Yeah could be a second trigger actually created or some weird state where the cron is duplicated internally at different colos or something 🤷
  • u
    @jonathan-masslight if you switch to the triggers tab and scroll to cron triggers can you screenshot that sections / ensure theres only one
  • j
    You think it's something I did, or a cloudflare thing?
  • j
    there is only one there
  • u
    Ok yeah its on cloudflares end then so not something you can really fix will make sure it gets noticed
  • j
    I did mess with cloudflare stuff a few weeks ago because there is an issue with the repo I'm using where deploys are now not working
  • j
    but that was a few weeks ago
  • k
    This documentation for testing multiple workers should note that ordering on initialization matters for parents and children: https://developers.cloudflare.com/workers/wrangler/api/#unstable_dev i.e. starting parents -> then children will make your tests fail
  • a
    Could you file an issue on the repo? https://github.com/cloudflare/cloudflare-docs/issues/new That will help make sure it doesn't get lost in Discord. Thanks!
  • r
    hello, any plan to release the new @Cloudflare/worker-types
  • r
    i found there are lack of type definition of 
    cloudflare:sockets
  • r
    i already saw the definition file in the repository but it is not released unfortunately
  • j
    I believe there's a release coming today/tomorrow that should fix those definitions 🙂
  • d
    as soon as https://github.com/cloudflare/workerd/pull/668 is merged, a release should go out
  • r
    thats awesome thanks
  • r
    btw any clue for this error? i just bootstrapped a pages with create-cloudflare

    https://cdn.discordapp.com/attachments/779390076219686943/1108847176496467969/image.pngâ–¾

  • j
    It's a very common issue: https://github.com/cloudflare/workers-sdk/issues/3262. workerd doesn't work with Debian 11 (and anything based off that, like Ubuntu 20), and likely other distros too
  • r
    sad. i guess this issue may caused by libc or sth
  • r
    okay some ugly workaround to make it work on arch. i soft linked 
    /usr/lib/libunwind.so
    to 
    ./node_modules/.bin/libunwind.so.1

    https://cdn.discordapp.com/attachments/779390076219686943/1108852406965506229/image.pngâ–¾

  • r
    when using 
    connect
    , what causes a stream to become "cancelled"?
  • r
    if the remote host closes the tcp connection, will I be unable to read any data it sent or something?
  • d
    Usually it implies the connection was unsuccessful, in which case no data can be read anyway. If you check the 
    closed
    promise you might see some more details (although right now it's likely to just resolve to a "Error: proxy request failed" exception).
  • j
    Workers quick edit is buggered for new workers. I am using free plan with 10ms cpu limit. I get a 10075 error saying I need the unbounded plan 
    workers.api.error.wrong_plan
    when trying to use quick edit. Any ideas how to fix?
  • u
    hmm thats weird it works fine for me what are the steps you do to get that? 🤔
  • j
    Not sure, seemed to happen when I started adding static pages websites
  • j
    Ugh, how do I get actual support for this? Anyone from cloudflare on I can speak with?
1...247824792480...2509Latest