Can any of the engineers see if there is a DNS resolution outage in singapore? Getting a ton of 530'

Lliam | helius.dev Can any of the engineers see if there is a DNS resolution outage in singapore? G...

U

Unsmart•12/15/23, 10:11 PM

its already on #cloudflare-status

L

liam | helius.devOP•12/15/23, 10:12 PM

ah wasn't there when I checked initially

L

liam | helius.devOP•12/15/23, 10:12 PM

ty

Original message was deleted

H

Hello, I’m Allie!•12/16/23, 10:34 AM

Since the assets are traveling through the Developer Platform(Workers), I would assume it wouldn’t be an issue, though it would also depend on the scale you are running at

J

Justintime•12/16/23, 4:17 PM

hello! I'm curious if anyone has a method for delaying the execution of

ctx.waitUntil()

ctx.waitUntil()

ctx.waitUntil()

ctx.waitUntil() until the primary

fetch()

fetch()

has returned or been canceled?

J

Janet S•12/16/23, 4:17 PM

Hello, I just launched the worker but it's showing me : DNS_PROBE_FINISHED_NXDOMAIN

J

Janet S•12/16/23, 4:17 PM

Does it take time to propogate?

J

Janet S•12/16/23, 4:18 PM

xxxxx.xxxxx.workers.dev default worker page

S

sanetram•12/16/23, 5:16 PM

oh how I love hyperoptimising workers to cut costs

S

sanetram•12/16/23, 5:17 PM

not in this pic is replacing wrangler esbuild with swc and turning the whole app in to a ternary

S

sanetram•12/16/23, 5:20 PM

not using routers => less global warming

S

sanetram•12/16/23, 5:22 PM

less parsing

S

sanetram•12/16/23, 5:23 PM

also tested and uses less memory

S

sanetram•12/16/23, 5:23 PM

S

sanetram•12/16/23, 5:25 PM

ah i guess im overthinking about the memory part but yeah ive seen a sizeable speedup switching from esbuild to swc + spack

S

sanetram•12/16/23, 5:26 PM

app is projected to handle 100 million requests a month

S

sanetram•12/16/23, 5:26 PM

thats a real number

K

kian•12/16/23, 5:26 PM

esbuild

esbuild

esbuild

esbuild will also do ternaries

K

kian•12/16/23, 5:27 PM

swc might have other optimisations, but it's not something Wrangler won't do

S

sanetram•12/16/23, 5:27 PM

hm should I open an issue for wrangler not minifying and mangling properly?

K

kian•12/16/23, 5:27 PM

That's a user choice

K

kian•12/16/23, 5:27 PM

Either add

minify = true

minify = true

minify = true

minify = true or

--minify

--minify

--minify

--minify to TOML/CLI

S

sanetram•12/16/23, 5:27 PM

oh my god i should read docs better

K

kian•12/16/23, 5:28 PM

export default {
  async fetch(req) {
    const { pathname } = new URL(req.url);

    if (pathname == "/foo") {
      return new Response("foo")
    }

    if (pathname == "/bar") {
      return new Response("bar")
    }

    return new Response("baz")
  }
}

export default {
  async fetch(req) {
    const { pathname } = new URL(req.url);

    if (pathname == "/foo") {
      return new Response("foo")
    }

    if (pathname == "/bar") {
      return new Response("bar")
    }

    return new Response("baz")
  }
}

export default {
  async fetch(req) {
    const { pathname } = new URL(req.url);

    if (pathname == "/foo") {
      return new Response("foo")
    }

    if (pathname == "/bar") {
      return new Response("bar")
    }

    return new Response("baz")
  }
}

export default {
  async fetch(req) {
    const { pathname } = new URL(req.url);

    if (pathname == "/foo") {
      return new Response("foo")
    }

    if (pathname == "/bar") {
      return new Response("bar")
    }

    return new Response("baz")
  }
}

var r={async fetch(n){let{pathname:e}=new URL(n.url);return e=="/foo"?new Response("foo"):e=="/bar"?new Response("bar"):new Response("baz")}};export{r as default};

var r={async fetch(n){let{pathname:e}=new URL(n.url);return e=="/foo"?new Response("foo"):e=="/bar"?new Response("bar"):new Response("baz")}};export{r as default};

var r={async fetch(n){let{pathname:e}=new URL(n.url);return e=="/foo"?new Response("foo"):e=="/bar"?new Response("bar"):new Response("baz")}};export{r as default};

var r={async fetch(n){let{pathname:e}=new URL(n.url);return e=="/foo"?new Response("foo"):e=="/bar"?new Response("bar"):new Response("baz")}};export{r as default};

K

kian•12/16/23, 5:28 PM

It's also useful when using build-time constants (via

define

define

define

define) because it'll do dead code elimination

K

kian•12/16/23, 5:29 PM

You can have a define of

ENVIRONMENT

ENVIRONMENT

ENVIRONMENT

ENVIRONMENT which can be

"dev"

"dev"

"dev"

"dev",

"prod"

"prod"

"prod"

"prod", etc - and have extra logging removed in your production build.

S

sanetram•12/16/23, 5:29 PM

yep got that working with swc

S

sanetram•12/16/23, 5:30 PM

i just tested with wrangler minify=true

S

sanetram•12/16/23, 5:30 PM

my output is twice as large due to no inlining

S

sty•12/17/23, 6:46 AM

limit for free worker is

10 milliseconds of CPU time per invocation

10 milliseconds of CPU time per invocation

10 milliseconds of CPU time per invocation

10 milliseconds of CPU time per invocation according to docs

how does that work if the worker is setup as a websocket client?
https://developers.cloudflare.com/workers/examples/websockets/#write-a-websocket-client

I want to setup a worker to connect to a remote ws server , get data, light processing on data, then store on KV or D1.

if worker is connected as a client to a remote ws server, wouldn't that eat up all the allotted 10ms almost instantly? its a little confusing.

Using the WebSockets API · Cloudflare Workers docs

WebSockets allow you to communicate in real time with your Cloudflare Workers serverless functions. In this guide, you will learn the basics of …

S

sty•12/17/23, 6:48 AM

i have a personal server using cloudflare tunnel and i have ws connections going on 24/7.
i can see in the systemctl logs that cpu time adds up to many days worth. not 10 milliseconds lol...

S

sty•12/17/23, 6:48 AM

hence my confusion. sorry if this was asked before

U

Unsmart•12/17/23, 6:55 AM

You dont use any CPU time unless you are actually processing messages. Waiting for messages wont use any CPU. So you can stay connected for quite some time depending on how much processing you do

S

sty•12/17/23, 6:55 AM

got it. thanks for the clarification. for long term processing where ws needs to be on 24/7, durable object is the way to go right?

U

Unsmart•12/17/23, 6:57 AM

I mean you can just reconnect, durable objects will still need reconnections eventually also. Should be less often with DOs but they will get restarted from time to time

S

sty•12/17/23, 7:00 AM

so basically, invoke the worker again on ws disconnect inside the same worker?

U

Unsmart•12/17/23, 7:02 AM

No I mean the client frontend should reconnect. You cant reconnect a socket from the server side and even if you could your worker invocation wouldnt exist anymore if it gets disconnected.

S

sty•12/17/23, 7:07 AM

my workflow goes like : get realtime ws data (as a client from remote server) -> store realtime data to persistent storage -> my clients can fetch data from storage without having to interact with the ws remote server

so i want the worker ws to be continually reconnecting after every eviction. the reconnect is not triggered by clients. is this feasible with workers?

R

ramesh prasad•12/17/23, 8:40 AM

@Unsmart | Tech debt my usecase is, when ever some thing happen on the server(workers), then server broadcast a message to the client and all the frontend(client) currenly connected right now should be able to get the same message from the server. What should i do to make this happen, a very simple example will be appreciated. And do i need to have durable object for this or just websocket connect is enough for this usecase?

R

ramesh prasad•12/17/23, 8:43 AM

and a quick question, can i debug websocket connect in the local environment? Currently everytime i make some changes, I am running

wrangler deploy

wrangler deploy

wrangler deploy

wrangler deploy

and connecting with frontend with

wss://projectULRhere.com

wss://projectULRhere.com

wss://projectULRhere.com

wss://projectULRhere.com

Can i make it easy for the development in local environment?

A

advaith•12/17/23, 9:04 AM

looks like the preview system in dash broke?

A

advaith•12/17/23, 9:04 AM

this worked fine a few days ago when i last edited the worker

A

advaith•12/17/23, 9:04 AM

K

KDX_MW | Kaddex.xyz / Ecko.xyz•12/17/23, 5:18 PM

Are cloudflare KV changes strongly consistent within the same global network location? i.e. if I make a change in SYD to a KV pair set the value to 1, will the next get immediately show '1' even if it was previously '0' as long as that request hits the SYD location?

KKDX_MW | Kaddex.xyz / Ecko.xyz Are cloudflare KV changes strongly consistent within the same global network loc...

H

Hello, I’m Allie!•12/17/23, 5:35 PM

Not explicitly, first because SYD is multiple colos, and second because cache writes can fail

HHello, I’m Allie!Not explicitly, first because SYD is multiple colos, and second because cache wr...

K

KDX_MW | Kaddex.xyz / Ecko.xyz•12/17/23, 5:55 PM

Is there a way to get the exact datacenter the user hits?

K

KDX_MW | Kaddex.xyz / Ecko.xyz•12/17/23, 5:56 PM

Not just the region?

K