Most people here use https://hono.dev as their framework but its more express-like than nest. Not su

M

MetalGear•5/7/24, 2:36 AM

I find nest js and spring boot just sooo capable in terms of building backends.

M

MetalGear•5/7/24, 2:36 AM

I meant using nestjs on something like GCP cloud run

M

MetalGear•5/7/24, 2:37 AM

I am one developer I love to code so much i do it 19 hours a day unhealthy lol. I am trying to build mvp backends that can handle a good amount of users.

M

MetalGear•5/7/24, 2:37 AM

I want to do it fast, spending way more time in learning to build backends then actually building thme

U

UnsmartOP•5/7/24, 2:38 AM

I mean if you already know and use nestjs on GCP cloud run you should probably just stick to that

UUnsmart Most people here use https://hono.dev as their framework but its more express-li...

M

MetalGear•5/7/24, 2:38 AM

I built an mvp with hono and cloudflare workers. I loved them

M

MetalGear•5/7/24, 2:39 AM

I just went away from that way of building backends because nest promised the whole domain driven design, hexagonal architecture, etc

M

MetalGear•5/7/24, 2:39 AM

I found it actually taught me how to build backends. While using and learning cloudflare i found no resources or path to learn to build well architected backends

U

UnsmartOP•5/7/24, 2:41 AM

Cloudflare doesnt really offer any opinions on how you should develope your workers. Workers is just a way to deploy applications like GCP cloud run. Nestjs is a framework. You cant really compare NestJS to Cloudflare workers

U

UnsmartOP•5/7/24, 2:42 AM

I'd imagine GCP cloud run doesnt really have any opinions on how you build your app either.

M

MetalGear•5/7/24, 2:50 AM

right but i guess cloudflare is just caught in the question of how can I build a robust and scalable backend on any cloudflare framework or whatever tools it is that we can use to accomplish our goal of a robust and capable easy to develop backend

M

MetalGear•5/7/24, 2:52 AM

with nest and ddd architecture I found really interesting and a buetiful way to write backends but got a bit overwhelmed. I constantly question is it necassary to use anything but cloudflare with typescript when very limited developers on the project

M

MetalGear•5/7/24, 2:54 AM

I guess im ultimately looking for someone to say hey im using this architecture for my backend with cloudflare workers succesfully and easily handling x amount of users

N

notjoemartinez•5/7/24, 4:38 AM

is there a way to try / catch cpu time limit errors or at least set the cors headers of errors that occur outside of the scope of your codes logic? When that happens it will cause a cors error on the client because it doesn't have a

Access-Control-Allow-Origin

Access-Control-Allow-Origin

set. I've even wrapped my workers entire logic in a try catch so the client side can actually view the response code/error but it seems like the worker throws the

Worker exceeded CPU time limit

Worker exceeded CPU time limit

Worker exceeded CPU time limit

Worker exceeded CPU time limit error outside of the scope of the program.

export default {
  async fetch(request, env, ctx) {
      try {
        // worker logic
      }
      catch (error) {
        let corsHeaders = {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "GET, OPTIONS, PUT, POST",
          "Access-Control-Allow-Headers": "*",
          'Content-Type': 'application/json',
          'status': 500
        }
        return new Response(JSON.stringify({ error: error.message }), {
          headers: corsHeaders
        });

      }
    }
}

export default {
  async fetch(request, env, ctx) {
      try {
        // worker logic
      }
      catch (error) {
        let corsHeaders = {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "GET, OPTIONS, PUT, POST",
          "Access-Control-Allow-Headers": "*",
          'Content-Type': 'application/json',
          'status': 500
        }
        return new Response(JSON.stringify({ error: error.message }), {
          headers: corsHeaders
        });

      }
    }
}

export default {
  async fetch(request, env, ctx) {
      try {
        // worker logic
      }
      catch (error) {
        let corsHeaders = {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "GET, OPTIONS, PUT, POST",
          "Access-Control-Allow-Headers": "*",
          'Content-Type': 'application/json',
          'status': 500
        }
        return new Response(JSON.stringify({ error: error.message }), {
          headers: corsHeaders
        });

      }
    }
}

export default {
  async fetch(request, env, ctx) {
      try {
        // worker logic
      }
      catch (error) {
        let corsHeaders = {
          "Access-Control-Allow-Origin": "*",
          "Access-Control-Allow-Methods": "GET, OPTIONS, PUT, POST",
          "Access-Control-Allow-Headers": "*",
          'Content-Type': 'application/json',
          'status': 500
        }
        return new Response(JSON.stringify({ error: error.message }), {
          headers: corsHeaders
        });

      }
    }
}

`

K

kian•5/7/24, 4:41 AM

You can't try/catch it, no - you might be able to use a Transform Rule to add the response headers but I haven't tried it.

U

UnsmartOP•5/7/24, 4:42 AM

if transform rules wouldnt work snippets should

K

kian•5/7/24, 4:48 AM

I'm not sure if it'll work either way

K

kian•5/7/24, 4:48 AM

Doesn't CORS not work regardless of headers on a non-OK status?

K

kian•5/7/24, 4:49 AM

:PE_PandaShrug:

N

notjoemartinez•5/7/24, 5:14 AM

Is the cpu time reset per request? I'm not even sure if my request is what is overloading the cpu time because it seems to trigger at a predictable number of requests of the same size.

const startTime = performance.now();
const res = await uploadPart(S3, request);
const endTime = performance.now();
const cpuTime = endTime - startTime;

console.log(`CPU Time: ${cpuTime} ms`);
return res;

const startTime = performance.now();
const res = await uploadPart(S3, request);
const endTime = performance.now();
const cpuTime = endTime - startTime;

console.log(`CPU Time: ${cpuTime} ms`);
return res;

const startTime = performance.now();
const res = await uploadPart(S3, request);
const endTime = performance.now();
const cpuTime = endTime - startTime;

console.log(`CPU Time: ${cpuTime} ms`);
return res;

const startTime = performance.now();
const res = await uploadPart(S3, request);
const endTime = performance.now();
const cpuTime = endTime - startTime;

console.log(`CPU Time: ${cpuTime} ms`);
return res;

This never logs more than 3500 ms and I cant see what the cpu time is set at when it does fail because it's outside of the programs logic. is there a "global cpu time" I'm not seeing?

K

kian•5/7/24, 5:15 AM

That's not measuring CPU time, it's measuring wall time.

K

kian•5/7/24, 5:15 AM

There is CPU rollover/grace - a handful of requests can go over, and requests going under means a few can go over, but consistently going over will result in the Worker being killed.

N

notjoemartinez•5/7/24, 6:06 AM

I found the median cpu time per request in the dashboard which exceeds the free tier 7ms. I upgraded to a standard account and everything worked. It would be nice to be able to log cpu time from within the workers code because I think I can reduce it by sending smaller requests. Thanks for your help though.

Y

Yakuzo•5/7/24, 9:47 AM

Hi, is it possible to make several external HTTP requests when calling a worker via RPC?
My worker doesn't want to wait for a response from my other worker even though everything is in await and I've tried putting Promises everywhere.
I'm making requests in a for loop, the first request is done correctly but doesn't want to wait for the response to this one

// Worker A
// Warning : 'await' has no effect on the type of this expression.
const result = await this.#ctx.env.MAIL_AUTH.mailVerify(mails);

// Worker A
// Warning : 'await' has no effect on the type of this expression.
const result = await this.#ctx.env.MAIL_AUTH.mailVerify(mails);

// Worker A
// Warning : 'await' has no effect on the type of this expression.
const result = await this.#ctx.env.MAIL_AUTH.mailVerify(mails);

// Worker A
// Warning : 'await' has no effect on the type of this expression.
const result = await this.#ctx.env.MAIL_AUTH.mailVerify(mails);

// Worker B
async mailVerify(mails: any): Promise<ReturnMailType> {
  return await new AuthManager(this.env).sendMailVerify(mails);
}

... // Deeper in the code ( in sendMailVerify(mails: any) ) in a for loop
const response = await fetch("https://api.brevo.com/v3/smtp/email", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "api-key": env.BREVO_API_KEY,
  },
  body: JSON.stringify(requestBody),
});

// No response
console.log("Response : ", response);

// Worker B
async mailVerify(mails: any): Promise<ReturnMailType> {
  return await new AuthManager(this.env).sendMailVerify(mails);
}

... // Deeper in the code ( in sendMailVerify(mails: any) ) in a for loop
const response = await fetch("https://api.brevo.com/v3/smtp/email", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "api-key": env.BREVO_API_KEY,
  },
  body: JSON.stringify(requestBody),
});

// No response
console.log("Response : ", response);

// Worker B
async mailVerify(mails: any): Promise<ReturnMailType> {
  return await new AuthManager(this.env).sendMailVerify(mails);
}

... // Deeper in the code ( in sendMailVerify(mails: any) ) in a for loop
const response = await fetch("https://api.brevo.com/v3/smtp/email", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "api-key": env.BREVO_API_KEY,
  },
  body: JSON.stringify(requestBody),
});

// No response
console.log("Response : ", response);

// Worker B
async mailVerify(mails: any): Promise<ReturnMailType> {
  return await new AuthManager(this.env).sendMailVerify(mails);
}

... // Deeper in the code ( in sendMailVerify(mails: any) ) in a for loop
const response = await fetch("https://api.brevo.com/v3/smtp/email", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "api-key": env.BREVO_API_KEY,
  },
  body: JSON.stringify(requestBody),
});

// No response
console.log("Response : ", response);

I'm getting a typescript alert that the “await” is not required when calling my entrypoint when it should be.
The request is correct, I have no errors and it is carried out correctly.

K

kian•5/7/24, 10:20 AM

Goooooooogle

K

kian•5/7/24, 10:20 AM

Thanks for pointing it out - https://github.com/cloudflare/cloudflare-docs/pull/14433

C

Chief•5/7/24, 12:58 PM

How can I use wrangler tail locally? It always looks for the deployed version of whatever env that I give it.

Also, is there a way to see correct stack traces for errors when running locally?

CChief How can I use wrangler tail locally? It always looks for the deployed version of...

H

Hello, I’m Allie!•5/7/24, 1:00 PM

Like tailing a local Worker?

HHello, I’m Allie!Like tailing a local Worker?

C

Chief•5/7/24, 1:00 PM

yeah

CChief yeah

H

Hello, I’m Allie!•5/7/24, 1:00 PM

wrangler dev

wrangler dev

should be logging it automatically, at least any console info

HHello, I’m Allie!`wrangler dev` should be logging it automatically, at least any console info

C

Chief•5/7/24, 1:01 PM

So it does log it, but I'm looking to get things like stack traces

 [wrangler:inf] POST /trpc/snapshots.getSnapshot 500 Internal Server Error (1795ms)

 [wrangler:inf] POST /trpc/snapshots.getSnapshot 500 Internal Server Error (1795ms)

 [wrangler:inf] POST /trpc/snapshots.getSnapshot 500 Internal Server Error (1795ms)

 [wrangler:inf] POST /trpc/snapshots.getSnapshot 500 Internal Server Error (1795ms)

I'd want more info while developing locally

CChief So it does log it, but I'm looking to get things like stack traces ``` [wrangler...

H

Hello, I’m Allie!•5/7/24, 1:03 PM

It should be logging stack traces by default. If it isn't, then you may be using a framework/middleware that is swallowing the errors

H

Hello, I’m Allie!•5/7/24, 1:04 PM

Only Uncaught Errors are loggged to the console, unless whatever is catching the errors is also logging them

C

Chief•5/7/24, 1:05 PM

That makes a lot of sense, i've added an

OnError

OnError

OnError

OnError to my TRPC server and it shows up now. Thanks for the help!

YYakuzo Hi, is it possible to make several external HTTP requests when calling a worker ...

Y

Yakuzo•5/7/24, 1:07 PM

Sorry, it was me who did a few things wrong... it's easy to get lost with several inter worker communications.

N

Nbc66•5/7/24, 4:08 PM

made a small worker script that can route statuspage.io website updates to discord webhooks

would love to see feedback on this. Thank you
https://gist.github.com/Nbc66/42cb525102be73a8d67f253fc84a9dcd

Gist

A Cloudflare Worker script to be used with statuspage.io websites t...

A Cloudflare Worker script to be used with statuspage.io websites that allow you to subscibe to updates using a webhook - GItHub_status_to_discord_webhook.js

N

Nbc66•5/7/24, 4:13 PM

here is how it would look like in discord
https://i.imgur.com/hmoMOrY.png
https://i.imgur.com/plsuami.png

Imgur

Imgur

S

Samir•5/7/24, 5:10 PM

Can I deploy Go API to cf workers?

SSamir Can I deploy Go API to cf workers?

C

Cyb3r-Jak3•5/7/24, 5:41 PM

You’d have to use something like https://github.com/syumai/workers.

C

codebam•5/7/24, 6:07 PM

hey can someone help me figure out why this action isn't working? https://github.com/kevinJ045/makibotto/actions/runs/8990189612/job/24694968263

GitHub

.... · kevinJ045/makibotto@2360aed

Contribute to kevinJ045/makibotto development by creating an account on GitHub.

C

codebam•5/7/24, 6:07 PM

it just says

 Error: Failed to upload secrets.
Error: 🚨 Action failed

 Error: Failed to upload secrets.
Error: 🚨 Action failed

 Error: Failed to upload secrets.
Error: 🚨 Action failed

 Error: Failed to upload secrets.
Error: 🚨 Action failed

C

codebam•5/7/24, 6:08 PM

there's an API key in

secrets and variables -> actions -> repository secrets

secrets and variables -> actions -> repository secrets

secrets and variables -> actions -> repository secrets

secrets and variables -> actions -> repository secrets

H

haters daddyhd from bulgaria•5/8/24, 12:17 AM

I want to make Wokers able to access banned foreign URLs for my country, how do I do it and I'm confused in this video session?

B

BallisticSwami•5/8/24, 10:20 AM

Currently what is the easiest way to connect workers to a MySQL db? Tried using the cloudflare-mysql npm package and even tried cloudflared tunneling but couldn't get it to work.

AAdam Cloudflare Workers can’t create TCP connections to port 25, so you’d likely stru...

S

Sheng•5/8/24, 11:12 AM

Hmm, which means I only can build the app somewhere else but not with Cloudflare :NotLikeThis:

Vvcoder Hello, Can anyone help how to use npm packages that uses node runtime core packa...

H

Hello, I’m Allie!•5/8/24, 2:21 PM

What packages do you need, specifically?

Vvcoder https://www.npmjs.com/package/ssh2

H

Hello, I’m Allie!•5/8/24, 2:25 PM

Sorry, I meant which Node-built-ins

Most people here use https://hono.dev as their framework but its more express-like than nest. Not su

Similar Threads

Similar Threads

Similar Threads