anyone else not able to deploy? sees like wangler login isn't working. Gate way error 504

DDenni It seems the library I'm using _does_ have a browser version you can build yours...

Denni•1/17/24, 5:13 PM

Okay, this doesn't quite seem to work either. Is it possible it's trying to access browser APIs that CF Workers don't have access to?

Denni•1/17/24, 5:14 PM

I'm not getting any build errors this time, it just doesn't work and throws warnings and tries to reconnect

kian•1/17/24, 5:15 PM

What package are you trying to use?

Denni•1/17/24, 5:17 PM

I'm using gramjs, a Telegram client. It has both a node and browser version

Denni•1/17/24, 5:17 PM

CF Workers might not be the best way to do this but I need something to automatically send a couple of telegram messages once per day

AAdvany anyone else not able to deploy? sees like wangler login isn't working. Gate way ...

AdvanyOP•1/17/24, 5:26 PM

working again

Deo Kumar•1/17/24, 8:15 PM

Does wasm binaries bundled using

wrangler deploy

wrangler deploy

count in 1MB limit?
Because my worker.js size is 940KiB and overall size including wasm is 2.3MiB after bundling but it throws the error

workers.api.error.script_too_large

workers.api.error.script_too_large

kian•1/17/24, 8:27 PM

Yes

AdvanyOP•1/17/24, 9:48 PM

mhhh... if I am doing wrangler dev (and I dont do await on a htmlrewrite transform), it doesnt work. But it works deployed when doing return rewriter.transform(response);

AdvanyOP•1/17/24, 9:50 PM

I should just do await then right?

AdvanyOP•1/17/24, 9:51 PM

In the docs there is no await so thats why I was confused!

kian•1/17/24, 9:54 PM

You can return a Promise from an async function (i.e the

fetch

fetch

handler) without awaiting it

AdvanyOP•1/17/24, 10:11 PM

yeah, I do that... but seems like when using locally (so without --remote) the htmlrewriter isn't running. Le tme create a sample project to show it

AA•1/18/24, 1:52 AM

need to find a nice way to create apis that can be consumed by workers. openapi seems so heavy these days.. tho maybe hono makes it nice

AA•1/18/24, 1:57 AM

using stuff like zodios/trpc and messing around with mono repos also an option i guess

Bob•1/18/24, 11:49 AM

I'm having a hard time grasping the worker concept of environment variables. I'm using hono and I want to create a variable outside hono 'c.env' context. I don't understand Where this 'env' comes from.

Bob•1/18/24, 11:53 AM

for example:

app.use('/input/*', bearerAuth({ TOKEN }));

app.use('/input/*', bearerAuth({ TOKEN }));

I would normally use 'process.env.TOKEN'

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

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

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));

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

Bob•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?

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

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

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

yes

BBob yes

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

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)

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

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

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

Bob•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...

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

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

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

Bob•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.

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

Thanks for your help!

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 ?

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

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

worker failed to prewarm: Service Temporarily Unavailable

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

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)
        }
    }
}

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

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

Maybe try #

rust-on-workers

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

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

Ooo ok! Will do!

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?

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

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

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

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

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...

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

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

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

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

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?

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

no, worker to worker is very special lol

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

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

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

but I actually do it already somewhere else

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) } } }

anyone else not able to deploy? sees like wangler login isn't working. Gate way error 504

Similar Threads

Similar Threads

Similar Threads