WWe're aware and Workers team is on it
I
MI've stepped back from helping the Node.js team on that
MI 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
Edit: Looks like the file limit bump was actioned, and then reverted, there is discussion in openjsf
IThen yeah, probably easier 
IThat's just very sad 
MBut yes, things like Actions/Pages probably should maintain their own caches of it instead of hitting Node's origin continually
WIt's on the roadmap
WWe just have a lot to do
IBut it's kind of becoming unbearable. I got like multiple build failures in the past week due to this
MOr equally, Cf could sponsor Node and given them cache reserve to make this problem go away
M'Cause Node.js origin is literally one tiny Droplet, that's it
MSo it's continually being overwhelmed by cache misses
WOh I agree, I'm pushing for us to do more at the min
ICan I sponsor a second one?
Coh that explains a lot
MThe other thing I'm still not sure I understand is why the origin is getting hit so hard
MIt should all be very cachable stuff, and with enough traffic to keep it cached for a while
CI had changed nothing in my pages function deploy and it broke, looks to be semi-fixed now
MYeah they do
QHey 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.
W
QAh, thanks!!
Qbut deployment went good and im happy
C
Ja3b764c3-5940-40a7-be15-175886942d6b
an internal error occurred, is the issue on my side or is the service down or something
an internal error occurred, is the issue on my side or is the service down or something
Ahey, is there a way to get Pages to notify me when a build fails?
Ausing the github automatic deployment integration thing
CThis feature is only available if your account has at least one paid feature. For more information, see our plans page.
Aah, so nothing built in?
Ai know there is a built in system that will comment on my PRs if the build fails
Aseems odd that would only exist for PRs, not for the main branch
CWhat do you mean by built in? If the build fails then it should show as a red X in the status for it
Ai mean specifically the built-in github integration
Ai'm looking for some kind of similarly built-in "email me if the build fails" option
Aor even better, show that red X on the github commit itself, like
CYou mean like this?
Ayeah! that would do it
CIt should be auto setup when you add the application
Aoh huh i see, it is, but strangely, i'm not getting notifications when it fails. i usually do. hmm.
CIt won't it isn't a GitHub action build. You would need to use a webhook to get active notifications
EIf you have a github webhook, they show there too
EIf you want emails, you can go to the notifications area, add a notification, set it to failed only and add an email address
JYou can access a KV binding via
If you wish to access the binding in
process.env.BINDING_NAME in your Next.js app when running a build with Wrangler/deploying to Pages/using next-on-pages' watch mode. With Wrangler locally, you pass the binding as an arg, like --kv=MY_KV. For deployments, you need to add the binding in your Pages project settings.If you wish to access the binding in
next dev, you could try using some kind of proxy like https://github.com/james-elicx/cf-bindings-proxy, which falls back to process.env in production builds.
JYeah, shouldn't be a problem. If there is something specific causing an issue please do let me know. To give an example, ISR pages are treated as static pages instead because we cannot do ISR on Pages
