for example: `app.use('/input/*', bearerAuth({ TOKEN }));` I would normally use 'process.env.TOKEN'

BBob for example: `app.use('/input/*', bearerAuth({ TOKEN }));` I would normally use ...

H

You would do something like

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

app.use('/input/*', (c, next) => bearerAuth({ c.env.TOKEN })(c, next));

HHello, I’m Allie!You would do something like ```ts app.use('/input/*', (c, next) => bearerAuth({ ...

B

BobOP•1/18/24, 12:04 PM

My hero! What it I just want to access them outside of the "app." context?

BBob My hero! What it I just want to access them outside of the "app." context?

H

Hello, I’m Allie!•1/18/24, 12:04 PM

Like, in the global scope? Is this for initializing a client or something?

B

BobOP•1/18/24, 12:04 PM

yes

BBob yes

H

Hello, I’m Allie!•1/18/24, 12:04 PM

Then you would initialize it within the

app

app

scope, then store it in a global

H

Hello, I’m Allie!•1/18/24, 12:05 PM

You could also use an AsyncLocalStorage to have it accessible globally(but that requires a compat flag)

H

Hello, I’m Allie!•1/18/24, 12:05 PM

But note, env vars are only ever available in the context of handling an incoming event

H

Hello, I’m Allie!•1/18/24, 12:05 PM

For example, you can't just pull a secret on startup

B

BobOP•1/18/24, 12:11 PM

ok, I guess I just have to repeat initialization code for each endpoint. I'm using Langhian and have to initialize the embeddings and vector store for every GET and POST. Is there a best practice?

BBob ok, I guess I just have to repeat initialization code for each endpoint. I'm usi...

H

Hello, I’m Allie!•1/18/24, 12:24 PM

You can have a single global variable to store them in, so they only get initialized once

H

Hello, I’m Allie!•1/18/24, 12:24 PM

Though note too that isolates aren’t reused very often, so it might be over optimization

H

Hello, I’m Allie!•1/18/24, 12:24 PM

Generally, they are only reused by the same client, in a limited period of time afterward

B

BobOP•1/18/24, 12:35 PM

yeah, It's more so about not having to repeat myself. I guess I can write a little wrapper function with all the static pieces and just call them with the envs with each event.

B

BobOP•1/18/24, 12:37 PM

Thanks for your help!

I

igorpancheski•1/18/24, 1:35 PM

Guys, i want to create a serverless function for converter .pst to .mbox, but the filesize can be heavy like 30gb or more. I need to understand if i can get a super power high processor and RAM for function on Workers of cloudfare. i finded to do it on aws or google but. i need a machine more stronger for my MVP. I don't care at first moment with the price i just want to validate my idea. someone has some option for helpme ?

Z

zegevlier•1/18/24, 1:37 PM

Workers are extremely unsuited for high memory requirement applications. They're not the right fit for your project

C

conqr ᯅ•1/18/24, 4:31 PM

worker failed to prewarm: Service Temporarily Unavailable

C

conqr ᯅ•1/18/24, 4:31 PM

?

C

captain_enjoyable•1/18/24, 4:35 PM

Hey there!

I'm trying to use the cache api, but running into issues. I have the follow minimal repro. When I ping this worker, I never get a "Cache hit" response. Any idea what might be going on here? I'm using the exact same key for every request.

async fn main(req: Request, env: Env, ctx: Context) -> Result<Response> {
    let cache = Cache::default();
    
    let path = "http://www.google.com";
    let response: Option<Response> = cache.get(path.clone(), false).await?;
    console_log!("here!");
    match response {
        Some(response) => {
            let mut resp: Response = Response::ok("Cache hit")?; 
            Ok(resp)
        }, 
        None => {
            console_log!("{}", path);
            let mut resp = Response::ok("Cache miss")?; 
            Ok(resp)
        }
    }
}

async fn main(req: Request, env: Env, ctx: Context) -> Result<Response> {
    let cache = Cache::default();
    
    let path = "http://www.google.com";
    let response: Option<Response> = cache.get(path.clone(), false).await?;
    console_log!("here!");
    match response {
        Some(response) => {
            let mut resp: Response = Response::ok("Cache hit")?; 
            Ok(resp)
        }, 
        None => {
            console_log!("{}", path);
            let mut resp = Response::ok("Cache miss")?; 
            Ok(resp)
        }
    }
}

async fn main(req: Request, env: Env, ctx: Context) -> Result<Response> {
    let cache = Cache::default();
    
    let path = "http://www.google.com";
    let response: Option<Response> = cache.get(path.clone(), false).await?;
    console_log!("here!");
    match response {
        Some(response) => {
            let mut resp: Response = Response::ok("Cache hit")?; 
            Ok(resp)
        }, 
        None => {
            console_log!("{}", path);
            let mut resp = Response::ok("Cache miss")?; 
            Ok(resp)
        }
    }
}

async fn main(req: Request, env: Env, ctx: Context) -> Result<Response> {
    let cache = Cache::default();
    
    let path = "http://www.google.com";
    let response: Option<Response> = cache.get(path.clone(), false).await?;
    console_log!("here!");
    match response {
        Some(response) => {
            let mut resp: Response = Response::ok("Cache hit")?; 
            Ok(resp)
        }, 
        None => {
            console_log!("{}", path);
            let mut resp = Response::ok("Cache miss")?; 
            Ok(resp)
        }
    }
}

Ccaptain_enjoyable Hey there! I'm trying to use the cache api, but running into issues. I have th...

H

Hello, I’m Allie!•1/18/24, 4:37 PM

Maybe try #

rust-on-workers

HHello, I’m Allie!Maybe try #🦀rust-on-workers

C

captain_enjoyable•1/18/24, 4:37 PM

Ooo ok! Will do!

S

sathoro•1/18/24, 4:56 PM

I'm getting a 522 when calling my Worker via its public custom domain from inside the same Worker, any ideas?

S

sathoro•1/18/24, 4:57 PM

its a blank route that just returns a 200. I can call it fine locally

U

Unsmart•1/18/24, 4:57 PM

Not surprising lots of issues with that I'd use service bindings

C

Chaika•1/18/24, 4:58 PM

or you could try seting the no miminal subrequests compat flag https://github.com/cloudflare/workerd/issues/787#issuecomment-1597396851

GitHub

🐛 BUG: Worker <-> Worker request over `custom_domain` returns insta...

Which Cloudflare product(s) does this pertain to? Workers/Other What version of Wrangler are you using? 2.9.0 What operating system are you using? Mac Describe the Bug Same zone worker <-> wo...

S

sathoro•1/18/24, 4:58 PM

why not surprising? it is just like calling any other API right?

S

sathoro•1/18/24, 4:58 PM

I'm using it to proxy webhook requests to the correct environment

S

sathoro•1/18/24, 4:58 PM

service bindings not gonna work for this use case

Ssathoro why not surprising? it is just like calling any other API right?

C

Chaika•1/18/24, 4:58 PM

no, worker to worker is very special lol

C

Chaika•1/18/24, 4:58 PM

you can't do same zone worker to worker with routes

S

sathoro•1/18/24, 4:58 PM

but I actually do it already somewhere else

S

sathoro•1/18/24, 4:59 PM

although I guess that is technically in a DO

U

Unsmart•1/18/24, 4:59 PM

Service bindings are actually a perfect use case for proxying to the correct env

why would it not work for you?

S

sathoro•1/18/24, 4:59 PM

ughh this is a big mess

C

Chaika•1/18/24, 5:00 PM

Worker to worker same-zone over routes > no
Worker to worker same-zone over Custom Domains -> should work, with compat flag?
Worker to worker different zones -> should work, will use worker ipv6
Worker to worker service bindings -> works and optimal, request doesn't go over network, fast

S

sathoro•1/18/24, 5:00 PM

did not expect this to not work

S

sathoro•1/18/24, 5:00 PM

does that flag actually work?

U

Unsmart•1/18/24, 5:00 PM

I'd personally suggest never calling your own worker with an outbound fetch and always using service bindings personally. Works the best and always

S

sathoro•1/18/24, 5:01 PM

yeah, I understand

S

sathoro•1/18/24, 5:01 PM

I don't need to code the extra logic of checking if the current worker is calling the same worker and then figuring out the binding when it should just work as is

C

Chaika•1/18/24, 5:02 PM

well my understanding is some of that complexity is needed because Workers can runs on routes and call the origin behind them

C

Chaika•1/18/24, 5:02 PM

wouldn't want to infinite loop

C

Chaika•1/18/24, 5:03 PM

custom domains were supposed to have the ability to act as a real origin and just work, and they did for a bit, but then got broken with the minimal subrequest stuff, so need compat flag

S

sathoro•1/18/24, 5:04 PM

thought I'd be making it easy on myself by putting this proxy in the worker instead of in a Supabase edge function, I guess I messed up

S

sathoro•1/18/24, 5:07 PM

no_minimal_subrequests

no_minimal_subrequests

no_minimal_subrequests

no_minimal_subrequests did not seem to work

S

sathoro•1/18/24, 5:12 PM

btw it works locally, of course. so did not spot the issue until now

S

sathoro•1/18/24, 5:18 PM

maybe I should proxy it through a DO

A

addison•1/18/24, 10:10 PM

hey, i have a quick question regarding billing

im piping files from Backblaze B2 through CF Workers and have a simple hono app that grabs files and sends them to the user

will the time it takes for this file to go to the user be counted under CPU time?

J

Jaden•1/19/24, 3:59 AM

Hi, Do Workers use CDN when serving data from R2 storage ? or can it be configured to use a CDN ?

for example: `app.use('/input/*', bearerAuth({ TOKEN }));` I would normally use 'process.env.TOKEN'

Similar Threads

Similar Threads

Similar Threads