I'm deploying with Github Actions and once it uploads I see the following error in the cf build dash

I'm deploying with Github Actions and once it uploads I see the following error in the cf build dashboard

11:17:25.909    Error: Failed to publish your Function. Got error: Unknown internal error occurred.

11:17:25.909 Error: Failed to publish your Function. Got error: Unknown internal error occurred.

11:17:25.909    Error: Failed to publish your Function. Got error: Unknown internal error occurred.

11:17:25.909 Error: Failed to publish your Function. Got error: Unknown internal error occurred.

shixzieOP•7/5/23, 4:22 PM

Sshixzie I'm deploying with Github Actions and once it uploads I see the following error ...

Cyb3r-Jak3•7/5/23, 4:23 PM

Ah that’s a different issue then. If you share your pages.dev domain then staff can look at the internal errors

shixzieOP•7/5/23, 4:23 PM

sure, fomace.pages.devfomace.pages.dev

Sshixzie sure, `fomace.pages.dev`

Cyb3r-Jak3•7/5/23, 4:24 PM

@Walshy if you get a chance

Walshy•7/5/23, 4:25 PM

Incident is happening

Walshy•7/5/23, 4:25 PM

We're aware and Workers team is on it

WWalshy Yeah sadly not much we can do...

itsmatteomanf•7/5/23, 4:29 PM

Just convince @MattIPv4 to move the downloads of Node.js versions to a R2-hosted subdomain? OMEGALUL

MattIPv4•7/5/23, 4:31 PM

I've stepped back from helping the Node.js team on that

MattIPv4•7/5/23, 4:31 PM

I wrote up a load of guidance a few months ago post-incident and none of it has been actioned afaik
Edit: Looks like the file limit bump was actioned, and then reverted, there is discussion in openjsf

Original message was deleted

itsmatteomanf•7/5/23, 4:31 PM

Then yeah, probably easier lul

MMattIPv4 I wrote up a load of guidance a few months ago post-incident and none of it has ...

itsmatteomanf•7/5/23, 4:31 PM

That's just very sad

MattIPv4•7/5/23, 4:32 PM

But yes, things like Actions/Pages probably should maintain their own caches of it instead of hitting Node's origin continually

Original message was deleted

Walshy•7/5/23, 4:35 PM

It's on the roadmap

Walshy•7/5/23, 4:35 PM

We just have a lot to do

itsmatteomanf•7/5/23, 4:35 PM

But it's kind of becoming unbearable. I got like multiple build failures in the past week due to this

MattIPv4•7/5/23, 4:35 PM

Or equally, Cf could sponsor Node and given them cache reserve to make this problem go away

MattIPv4•7/5/23, 4:35 PM

'Cause Node.js origin is literally one tiny Droplet, that's it

MattIPv4•7/5/23, 4:36 PM

So it's continually being overwhelmed by cache misses

Iitsmatteomanf But it's kind of becoming unbearable. I got like multiple build failures in the ...

Walshy•7/5/23, 4:38 PM

Oh I agree, I'm pushing for us to do more at the min

MMattIPv4 'Cause Node.js origin is literally one tiny Droplet, that's it

itsmatteomanf•7/5/23, 4:39 PM

Can I sponsor a second one? lul

WWalshy Incident is happening

Catt0s•7/5/23, 4:39 PM

oh that explains a lot

MattIPv4•7/5/23, 4:39 PM

The other thing I'm still not sure I understand is why the origin is getting hit so hard

MattIPv4•7/5/23, 4:40 PM

It should all be very cachable stuff, and with enough traffic to keep it cached for a while

Catt0s•7/5/23, 4:40 PM

I had changed nothing in my pages function deploy and it broke, looks to be semi-fixed now

MattIPv4•7/5/23, 4:42 PM

Yeah they do

quambo•7/5/23, 4:42 PM

Hey guys, any chance you can add error messages in failed cloudflare pages deployments? Its really hard to figure what went wrong currently. E.g., a few days ago I tried to deploy with a function that exceeded size, and it looked like it worked via zip upload. But the dashboard showed a failure with no error. Now, after I had things working, I had a random failure showing without context.

Walshy•7/5/23, 4:46 PM

https://www.cloudflarestatus.com/incidents/dy5420gy6dmt incident publishing Functions is resolved