Oh, I thought you said it multiplies it by number of cores?

HHello, I’m Allie!Oh, I thought you said it multiplies it by number of cores?

I

Isaac McFadyen•4/7/24, 12:55 PM

No, so if you cap 4 cores at 100%, then in 1 wall-clock second you'll consume 4 cpu-time seconds.

I

Isaac McFadyen•4/7/24, 12:55 PM

But if you wanted to do the same task on a single core, then you'd cap that single core at 100% for 4 wall-clock seconds and consume the same 4 cpu-time seconds (assuming the scaling was linear)

IIsaac McFadyen No, so if you cap 4 cores at 100%, then in 1 wall-clock second you'll consume 4 ...

H

Hello, I’m Allie!OP•4/7/24, 12:56 PM

I was also just referring to while you can pretty easily figure out single core pricing, by timing total duration length, then subracting I/O, it would be a bit more complex for multicore

HHello, I’m Allie!I was also just referring to while you can pretty easily figure out single core ...

I

Isaac McFadyen•4/7/24, 12:57 PM

Yeah... I'm not sure.

H

Hello, I’m Allie!OP•4/7/24, 12:57 PM

Since while a request may take 5 cores 10 seconds to process, you don't know if it is utilizing all 5 cores the entire time

AAnay-208 How to see cores capped then?

I

Isaac McFadyen•4/7/24, 1:00 PM

Sorry, I kind of went on a tangent - this isn't related to your use-case at all.

I

Isaac McFadyen•4/7/24, 1:00 PM

You just need to look at the CPU Time measurements on the Cloudflare dashboard. On the free plan you get 10ms of CPU time, on the paid plan you get up to 30s.

Lluna https://blog.cloudflare.com/pages-workers-integrations-monorepos-nextjs-wrangler...

J

James•4/7/24, 2:27 PM

Fun fact: you could create next-on-pages projects without needing to do additional setup for a long time. The pages project create command accepts a compatibility flags argument which automatically sets the flag in your new project

JJames Fun fact: you could create next-on-pages projects without needing to do addition...

L

luna•4/7/24, 2:29 PM

huh? that doesn’t answer the question at all.

J

James•4/7/24, 2:46 PM

kind of. you said you can't push a next-on-pages project without having to set it up in the dashboard, but it's always been possible to do that have the compat flag added when creating the project. sorry, not a helpful response to you i know.

J

James•4/7/24, 2:46 PM

anyway, looking at the changelog for wrangler there's been nothing to change the new behaviour

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/8/24, 1:15 AM

is there a entry point for installing an application-level instance of asynclocalstorage?

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/8/24, 1:15 AM

for next-on-pages

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/8/24, 1:17 AM

i could wrap all my /api/ handlers (and server components if that works)

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/8/24, 1:17 AM

but if there's one place, i'd rather do that

Ss̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜is there a entry point for installing an application-level instance of asyncloca...

J

James•4/8/24, 7:00 AM

There is not. Are you able to share an example use case you're thinking of for being able to do so?

D

Djekel•4/8/24, 7:03 AM

Hi all, if I want to use turso db with a full stack nextjs app deployed on pages, do I need to initialize the db on every next API endpoints? Or can I just create a file and export the db and import to endpoints could it work?

B

Berlin•4/8/24, 7:17 AM

Hi all, Cloudflare page not working NextJS14 Node v18.17.1

BBerlin Hi all, Cloudflare page not working NextJS14 Node v18.17.1

H

Hello, I’m Allie!OP•4/8/24, 7:20 AM

What is your deploy command?

H

Hello, I’m Allie!OP•4/8/24, 7:20 AM

Should be something like

wrangler pages deploy .vercel/output/static

wrangler pages deploy .vercel/output/static

wrangler pages deploy .vercel/output/static

wrangler pages deploy .vercel/output/static

J

James•4/8/24, 7:28 AM

yeah that looks like using the wrong output directory

B

Berlin•4/8/24, 7:33 AM

I changed the build configurations

TTaylor So, I'm wanting to use Drizzle + Turso DB. Are there any specific gotchas I need...

D

Djekel•4/8/24, 7:53 AM

Hi, there can I ask how did managed using turso with nextjs?

M

MylesBolton•4/8/24, 8:31 AM

ok so got allot of stuff working but i am trying to debug my pages but the errros keep showing up like this

  "logs": [
    {
      "message": [
        "Failed to Send Email:",
        "[object Object]"
      ],
      "level": "error",
      "timestamp": 1712562394309
    }
  ],

  "logs": [
    {
      "message": [
        "Failed to Send Email:",
        "[object Object]"
      ],
      "level": "error",
      "timestamp": 1712562394309
    }
  ],

  "logs": [
    {
      "message": [
        "Failed to Send Email:",
        "[object Object]"
      ],
      "level": "error",
      "timestamp": 1712562394309
    }
  ],

  "logs": [
    {
      "message": [
        "Failed to Send Email:",
        "[object Object]"
      ],
      "level": "error",
      "timestamp": 1712562394309
    }
  ],

is there any way for it to show the actual data it was passed instead of object ?

M

MylesBolton•4/8/24, 8:41 AM

migh hvae figured it out

D

Djekel•4/8/24, 11:08 AM

Anyone used turso with nextjs?

D

Djekel•4/8/24, 11:09 AM

In the web UI there only D1 biding integration

N

Nob•4/8/24, 3:54 PM

Hey, I just found out that nextjs default image resizing doesn't work with next on pages, is this intended?

N

Nob•4/8/24, 3:54 PM

The returned image is always at its original size

J

James•4/8/24, 4:49 PM

yes, it's not possible for us to do image resizing on the server in pages until the images team adds support to do that

B

bun•4/8/24, 6:02 PM

src/server/utils.ts

import 'server-only'

export function getEnv(): Env {
  const grc = getRequestContext().env as unknown as Env;

  if (grc.SECRET_KEY != null) {
    return grc;
  } else if (process.env.SECRET_KEY != null) {
    return process.env as unknown as Env;
  } else {
    throw new Error("Env variables are not defined");
  }
}

import 'server-only'

export function getEnv(): Env {
  const grc = getRequestContext().env as unknown as Env;

  if (grc.SECRET_KEY != null) {
    return grc;
  } else if (process.env.SECRET_KEY != null) {
    return process.env as unknown as Env;
  } else {
    throw new Error("Env variables are not defined");
  }
}

import 'server-only'

export function getEnv(): Env {
  const grc = getRequestContext().env as unknown as Env;

  if (grc.SECRET_KEY != null) {
    return grc;
  } else if (process.env.SECRET_KEY != null) {
    return process.env as unknown as Env;
  } else {
    throw new Error("Env variables are not defined");
  }
}

import 'server-only'

export function getEnv(): Env {
  const grc = getRequestContext().env as unknown as Env;

  if (grc.SECRET_KEY != null) {
    return grc;
  } else if (process.env.SECRET_KEY != null) {
    return process.env as unknown as Env;
  } else {
    throw new Error("Env variables are not defined");
  }
}

is this fine?

getRequestContext()

getRequestContext()

getRequestContext()

getRequestContext() and

process.env

process.env

is still very confusing. sometimes they work in local, sometimes they dont work in prod, so i made this utility function

B

bun•4/8/24, 6:02 PM

right now process.env works on local, but getRequestContext doesn't, when it always did in the past, very weird

Bbun src/server/utils.ts ```ts import 'server-only' export function getEnv(): Env { ...

D

Dario•4/8/24, 8:14 PM

both

getRequestContext()

getRequestContext()

getRequestContext()

getRequestContext() and

process.env

process.env

should with

next dev

next dev

next dev

next dev,

wrangler pages dev

wrangler pages dev

and production
(and you should ideally always use

getRequestContext()

getRequestContext()

getRequestContext()

getRequestContext())

If either doesn't work in some scenario, could you please open an issue (ideally with a minimal reproduction): https://github.com/cloudflare/next-on-pages/issues/new?assignees=&labels=bug&projects=&template=bug-report.yml&title=%5B%F0%9F%90%9B+Bug%5D%3A+

so that I can take a look and address the bug?

(most definitely you should not have to define utility functions like the one you shared!

)