Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 10:17:05.159 ▲ in

Segmentation fault
10:17:05.158 ▲ error Command failed with exit code 139.
10:17:05.159 ▲ info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
10:17:05.174 ▲ Error: Command "yarn run build" exited with 139
10:17:05.250 ▲ error Command failed.
10:17:05.251 ▲ Exit code: 1
10:17:05.251 ▲ Command: vercel
10:17:05.251 ▲ Arguments: build
10:17:05.251 ▲ Directory: /opt/buildhome/repo
10:17:05.251 ▲ Output:
10:17:05.251 ▲ info Visit https://yarnpkg.com/en/docs/cli/exec for documentation about this command.
10:17:05.265
10:17:05.265

The Vercel build (

yarn exec vercel -- build

yarn exec vercel -- build

yarn exec vercel -- build

yarn exec vercel -- build) command failed. For more details see the Vercel logs above.
10:17:05.266

If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.

Rrabbit1920 Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 1...

James•6/27/24, 9:31 PM

Segmentation fault will likely be an issue with either how Next.js builds, or how the Vercel CLI processes it.

Rrabbit1920 Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 1...

Nob•6/27/24, 11:27 PM

@rabbit1920 is it crashing if you build in local ?

Nneoney gives me stuff like "ReferenceError: async__chunk_24831 is not defined" in prod ...

Alec | Kriebel LLC.•6/28/24, 2:05 AM

I also receiving this after upgrading to Next.js 14, from 13. It's causing my site to return 500 http, which means Google has stopped indexing and showing my site in search results.

Anyone have any solutions to this?

James•6/28/24, 6:11 AM

I'll upgrade one of my projects to next14 at some point next week and see if I can get the same problem to look into it

JJames I'll upgrade one of my projects to next14 at some point next week and see if I c...

Alec | Kriebel LLC.•6/28/24, 3:26 PM

Thank you! I've confirmed that downgrading to Next.js 13 without other code changes does indeed fix this issue. Let me know how if I can help out.

Original message was deleted

Nob•6/28/24, 5:02 PM

you have to prerender the routes

Nob•6/28/24, 5:50 PM

perfect

Nob•6/28/24, 5:50 PM

aspecs•6/30/24, 4:23 AM

Someone explain to me when my last deployment was over 16 hours ago why the cache is STILL not cleared cry

aspecs•6/30/24, 4:23 AM

ignore sentry errors btw

aspecs•6/30/24, 4:27 AM

I shouldnt have to clear it myself if I have a custom domain setup

aspecs•6/30/24, 4:27 AM

it should j do it

Oreki•7/1/24, 7:03 AM

hello i am facing an issue with next-on-pages, where it is asking me to use edge runtime, even tho i am turning off the dynamicParams and want to pre-render the pages

The structure is like this

[path]/
  [...slug]/
    page.tsx (should be pre-rendered)
  page.tsx (should be pre-rendered)

[path]/
  [...slug]/
    page.tsx (should be pre-rendered)
  page.tsx (should be pre-rendered)

FrostTaco•7/1/24, 12:51 PM

With the error

Failed to publish your Function. Got error: Your Functions script is over the 1 MiB size limit

Failed to publish your Function. Got error: Your Functions script is over the 1 MiB size limit

Is there any way to know what specifically is causing the error?

FrostTaco•7/1/24, 1:00 PM

nvm I think I found it, but do server actions combine their size with where they're used? bc it seems like that's what's happening which really doesn't make much sense to me

FFrostTaco With the error `Failed to publish your Function. Got error: Your Functions scrip...

Nob•7/1/24, 7:02 PM

pay the 5$ sub

FFrostTaco nvm I think I found it, but do server actions combine their size with where they...

Isaac McFadyen•7/1/24, 7:58 PM

Yes, they do.

Isaac McFadyen•7/1/24, 7:58 PM

Your entire Next server-side code is bundled into one, so it needs to be (combined) under the limit.

IIsaac McFadyen Your entire Next server-side code is bundled into one, so it needs to be (combin...

FrostTaco•7/1/24, 11:34 PM

Doesn't make all too much sense when the server actions are only being called client side though

ZeroReturner•7/2/24, 1:07 AM

does edge runtime actuall work? All my page return 404 with edge runtime, It does not work with this simplest demo:

// src/app/page.tsx
export const runtime = "edge";

export default function Home() {
return <div>Hello from the edge!</div>;
}

FFrostTaco Doesn't make all too much sense when the server actions are only being called cl...

Hard@Work•7/2/24, 9:10 AM

I'm not sure I understand your point? Yes, they are invoked by something on the client, but they still run on the server, and thus must obey the size limits the server has

HHard@Work I'm not sure I understand your point? Yes, they are invoked by *something* on th...

FrostTaco•7/2/24, 9:31 AM

I don't understand why they're being bundled together with the page, pushing it over the size limit. It's like if all my API routes got combined into one, and then also got combined with the pages in which they're used. It wouldn't make much sense, because they should all be independent and all have their own size limit.

I may be using them wrong but I'm using server actions as a replacement for my API routes(at least ones that mutate data), but it seems that just using them instead makes for a less efficient app because everythings bundled together like it wouldn't otherwise be?
(I do realize I can easily avoid this problem by just using API routes instead but that's much less convenient)

FFrostTaco I don't understand why they're being bundled together with the page, pushing it ...

Hard@Work•7/2/24, 9:51 AM

It's not being bundled with the page. All things that happen on the server(SSR stuff, Server Actions, API Routes, the actual Router) are uploaded together, and if they go over the limit, then it throws that error

HHard@Work It's not being bundled with the page. All things that happen on the server(SSR s...

FrostTaco•7/2/24, 10:14 AM

So that error means all my server code combined is too big?

FFrostTaco So that error means all my server code combined is too big?

Hello, I’m Allie!•7/2/24, 10:34 AM

Yes, though as Nob noted, the Paid Workers plan has larger Server size limits

FrostTaco•7/2/24, 11:34 AM

How can I determine how big my site(or whatever is included in the size of a function) actually is then? I thought it might be

.vercel/output/static/_worker.js

.vercel/output/static/_worker.js

but that's only 27KB for me

FFrostTaco How can I determine how big my site(or whatever is included in the size of a fun...

Hard@Work•7/2/24, 11:35 AM

Do you see any import statements within that file?

FrostTaco•7/2/24, 12:05 PM

I do but they're dynamic without exact paths.
Looks like maybe it's importing things in

__next-on-pages-dist__/functions/

__next-on-pages-dist__/functions/

in which case there is a file there that's over 1MB.
That file though has the name of the route to my page I used the server actions on. The server actions are quite literally what my API routes were(and looking through old build logs the API routes totaled < 100KB).
I'm trying to convert back to API routes to see what happens. Could be maybe that compression or minimization is worse when everything is in one route?

FFrostTaco I do but they're dynamic without exact paths. Looks like maybe it's importing th...

Hard@Work•7/2/24, 12:10 PM

It shouldn't be

FrostTaco•7/2/24, 12:57 PM

Ok think I figured out my issue... My page was static before, but I forgot I switched it to the edge runtime to use actions...

Knowing I can't use edge runtime without being over the max size, without paying I really am just going to have to stick to API routes?

FFrostTaco Ok think I figured out my issue... My page was static before, but I forgot I swi...

Nob•7/2/24, 4:06 PM

you should be able to use server actions without paying

Nob•7/2/24, 4:06 PM

maybe you use a lib thats too big

st•7/3/24, 3:52 PM

export async function getData(slug: string) {
  
  const response = await fetch(
    `https://data.retuning/api/data/${slug}`,
    {
      headers: {
        "Api-Access-Key": "XXXX",
      },
    }
  );

  const slugResult = (await response.json()) as unknown as SlugData;

  return slugResult;
}

export async function getData(slug: string) {
  
  const response = await fetch(
    `https://data.retuning/api/data/${slug}`,
    {
      headers: {
        "Api-Access-Key": "XXXX",
      },
    }
  );

  const slugResult = (await response.json()) as unknown as SlugData;

  return slugResult;
}

`

When I try use cache keys in fetch request, I get "The 'cache' field on 'RequestInitializerDict' is not implemented." What is the correct way of caching this data with next-on-pages?

st•7/3/24, 3:59 PM

Documentation(https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/docs/caching.md) is very vague, it first says "Caching in Next.js applications (thus applications built using @Cloudflare/next-on-pages as well) is enabled by default." But then, it talks about two storage options. There is no sample for either option...

GitHub

next-on-pages/packages/next-on-pages/docs/caching.md at main · clou...

CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages

Sst ```js export async function getData(slug: string) { const response = await ...

st•7/3/24, 5:56 PM

By the way, If I leave this as it is data is not cached...

Sst ```js export async function getData(slug: string) { const response = await ...

ixixix•7/3/24, 9:21 PM

The

cache

cache

field doesn't work on workers runtime. You can try

next.revalidate: false

next.revalidate: false

to force cache

ixixix•7/3/24, 9:22 PM

https://nextjs.org/docs/app/api-reference/functions/fetch#optionsnextrevalidate

Functions: fetch | Next.js

API reference for the extended fetch function.

st•7/3/24, 10:47 PM

i did that, but it's not working either, maybe I am having the same issue with these guys: https://github.com/cloudflare/next-on-pages/issues/799

GitHub

[🐛 Bug]: Next fetch caching having issues in next-on-pages@1.11.3 ·...

next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:17:33 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6031 CPU...

st•7/3/24, 10:51 PM

i started using my own implementation

const cache = await caches.open(name);

let response = await cache.match(buildCacheKey(key));

...

getRequestContext().ctx.waitUntil(
      cache.put(buildCacheKey(key), response.clone())

const cache = await caches.open(name);

let response = await cache.match(buildCacheKey(key));

...

getRequestContext().ctx.waitUntil(
      cache.put(buildCacheKey(key), response.clone())

st•7/3/24, 10:51 PM

and it's working, so I guess something is broken with the library

AAlec | Kriebel LLC.Thank you! I've confirmed that downgrading to Next.js 13 without other code chan...

James•7/4/24, 10:50 AM

Hi again. I've upgraded my cloudy repo to Next.js 14.2.4 but I'm not encountering this issue. Is there any specific logic happening on pages/routes where you're encountering it?

FFrostTaco I don't understand why they're being bundled together with the page, pushing it ...

James•7/4/24, 10:52 AM

Calling an action makes a HTTP request to the current page the action is being called from, so their code is included as part of the function for the page.

Rohit Verma•7/4/24, 11:36 PM

Can I create an async queue consumer or is there any other way to perform an action in background/ response a for webhook

Aalejoskyhitz Hey everyone! I'm getting this as well and it is so bad, it completely blows up ...

dzoni•7/5/24, 11:30 AM

I had a similar error, fixed with the edge runtime included in my server side component

whois | API man•7/5/24, 8:06 PM

I have a server side component (/api) that does the connection between Resend and my app.

My question is, I have to do something on my Cloudflare Dashboard so that this works?

whois | API man•7/5/24, 8:07 PM

Because before I deployed my app it worked and after deploying it, it gives Internal Server Error

James•7/6/24, 9:22 AM

what is the error that it's logging

Sheng•7/7/24, 1:35 AM

Does anyone know how to run a cronjob with next-on-pages, nextjs 14?

SSheng Does anyone know how to run a cronjob with next-on-pages, nextjs 14?

Hello, I’m Allie!•7/7/24, 8:05 AM

Pages doesn’t support Crons

nxc•7/7/24, 11:28 PM

Hey all

I deployed a fresh nextjs app using pages + wrangler and its awesome!

I have an existing nextjs app that was not bootstrapped using

npx create cloudflare

npx create cloudflare

I'm wondering if its possible to opt-in after the fact and still be able to deploy to cloudflare?

Segmentation fault 10:17:05.158 ▲ error Command failed with exit code 139. 10:17:05.159 ▲ in

Similar Threads

Similar Threads

Similar Threads