is there any way to create folders in the dashboard where all workers and pages are listed so to gro
is there any way to create folders in the dashboard where all workers and pages are listed so to group them by projects?
CUnfortunately not
Bis this something in the roadmap? I thought this is something that most people would want to use. or am I being biased? now when I heavily use cloudflare for many small projects I spent a lot of time finding my workers and pages.
TYou are one pages project and few API calls away from it
Dyou mean like a SOCKS-like proxy service that works with Workers?
Syeah through HTTPS endpoint that has dedicated IP support
S"that has dedicated IP support" this is the part I can't find
SI already have rotating proxies with HTTPS endpoints
Dwhat's the reasoning behind needing a dedicated IP from a third party? Why not use your own?
Smy own IP, from where?
Dthose work with Workers?
Sthere is a host that has completely blocked all incoming workers
Sand we have lots of users that use that host for an integration
Sand they won't work with us
Sof course because its a normal HTTPS call
Sno proxy config
Dhuh interesting, could you show an example fetch?
SDoh, that ,makes more sense lol. I was thinking it was a straight up standard HTTP proxy
Dwhy not spin up an instance on DigitalOcean or something? 
Dor is it a scaling problem too?
SI have a feeling that will be blocked already but yeah that is the next move if this doesn't work. this was supposed to be the easiest option but nobody offers it..
Smight just use rotating residential proxy should work
Din theory you could use outbound TCP sockets and connect to a "normal" HTTP or SOCKS proxy.
Lany idea why returning a 401 from a gRPC service would cause CF LB to return a 520? It doesn't return 520 if I made a http1 call to the same server w same response
UWhen troubleshooting most 5XX errors, the correct course of action is to first contact your hosting provider or site administrator to troubleshoot and …
LNone of these are relevant, its something up with gRPC handling
NDoes @cf/meta/llama-2-7b-chat-int8 in Workers AI have a token restriction that generates incomplete results
EA better channel is #workers-ai-beta
But yes, there are limits here: https://developers.cloudflare.com/workers-ai/platform/limits/
But yes, there are limits here: https://developers.cloudflare.com/workers-ai/platform/limits/
EAlso @ndy please try to avoid sending your question to multiple channels as this can cause confusion and duplicate efforts
CGRPC doesn't have 401s... what GRPC code are you returning?
what GRPC code are you returning?Lset grpc-status header to PERMISSION_DENIED but didn't change anything
Care you using some sort of GRPC gateway?
LUsing envoy
LHave a wasm plugin that for eg. will return 401 if no api key is present
Lfor http1 this works, for grpc the LB returns 520
CWhat that sounds like to me is the gateway you are using is translating the GRPC -> to http1 error codes incorrectly
Cwhen the grpc request is authenticated does it work correctly?
LYep it does
Cyeah, so cloudflare part is working
LIf the code just responds with a 401, grpc-status header set, what else could be missing?
Cenvoy config could be wrong
PSo to use Pages advanced mode I have to use this https://developers.cloudflare.com/pages/platform/functions/advanced-mode/
I did follow the docs, but like im struggling with putting the _worker.js in the actual output dir??
Like as you can see in the first photo, running the build command generates a _worker.js file, but it is not the one that I wrote, how do I get MY worker to be in the build directory? Keep in mind I'm using svelte
I did follow the docs, but like im struggling with putting the _worker.js in the actual output dir??
Like as you can see in the first photo, running the build command generates a _worker.js file, but it is not the one that I wrote, how do I get MY worker to be in the build directory? Keep in mind I'm using svelte
PThis is my wrangler.toml file, it is worth noting that my worker is located in /worker/index.js
EIf you switch your Worker to the new Standard pricing (or even the old Unbound pricing), the subrequest limit will be 1000 instead of 50
ISvelteKit uses their own _worker.js, what is your purpose for using _worker.js? Also we should probably be talking in #functions
Palr we can move there
