Jeff
CDCloudflare Developers
•Created by Jeff on 7/18/2024 in #workers-help
do-taskmanager with rpc
That would be amazing!
4 replies
CDCloudflare Developers
•Created by Jeff on 7/18/2024 in #workers-help
do-taskmanager with rpc
cc @Erwin if he's available? 😄
4 replies
CDCloudflare Developers
•Created by Jeff on 5/29/2024 in #pages-help
node-gyp issues
Just got this back from support. Unfortunately it had been 2 weeks and I just ended up adding
node-gyp
to deps, which seems fine so far7 replies
CDCloudflare Developers
•Created by Jeff on 5/29/2024 in #pages-help
node-gyp issues
Reported this to paid support, will post back if we figure it out !
7 replies
CDCloudflare Developers
•Created by Jeff on 5/29/2024 in #pages-help
node-gyp issues
Caching is disabled and we're on build system V2
7 replies
CDCloudflare Developers
•Created by Jeff on 5/29/2024 in #pages-help
node-gyp issues
We have:
7 replies
CDCloudflare Developers
•Created by Jeff on 5/29/2024 in #pages-help
node-gyp issues
Deployment ID:
138da382-d26d-44ff-86d0-c01713682651
(after pressing retry a few times) builds, no error code 17 replies
CDCloudflare Developers
•Created by Jeff on 3/23/2024 in #next-on-pages
It seems that passing of specific `x-
Hello, I inherited this project from a client that probably broke some no-nos, but basically we were using:
https://create.t3.gg/
in nextjs app dir
and this
headers()
call was returning a header cf-connecting-ip
that was problematic, as Erisa pointed out in the main channel.
Unclear to me why, maybe something server components related, or maybe that shouldn't have been passed "headers" obj on the UI side.
Because of this, the requests from the UI to x.pages.dev was blocked on CF side, error code 1000
I wish I could provide more but am currently too busy2 replies