Are you running into issues with how it is now? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

kian

Kkian Are you running into issues with how it is now?

sokorototo

S

sokorototo•5/25/23, 9:47 PM

Not necessarily issues, but I had to re-architecture around this

sokorototo

S

sokorototo•5/25/23, 9:47 PM

Seems like an easy quality of life improvement

sokorototo

S

sokorototo•5/25/23, 9:47 PM

Now I can't use the nice Router

sokorototo

S

sokorototo•5/25/23, 9:47 PM

Is there a reason why it's not using a closure tho?

kian

K

kianOP•5/25/23, 9:48 PM

It'll just coerce closures as long as they're not capturing any vars so I've never had an issue with it personally

kian

Kkian It'll just coerce closures as long as they're not capturing any vars so I've nev...

sokorototo

S

sokorototo•5/26/23, 6:58 AM

But what if i want to capture variables

sirupsen

Ssirupsen Put them in `with_data`

sokorototo

S

sokorototo•5/26/23, 10:57 AM

Ah, I see

kian

K

kianOP•5/26/23, 7:02 PM

Isolates are per metal rather than per colo so whilst isolates tend to hang around for a long time (I stopped counting the highest I’ve seen at 22 hours), actually hitting an existing one unless you’ve got a connection already alive is a bit of a pain

kian

K

kianOP•5/26/23, 7:11 PM

I guess it depends on what you're storing / how intensive/slow it is when you have a miss

kian

K

kianOP•5/26/23, 7:12 PM

Global scope is super fast but per isolate, cache is per colo, KV has two central stores but is just as fast as cache when hot and then R2/DO are stored in <region>.

kian

K

kianOP•5/27/23, 5:12 PM

Try npx wrangler generate <NEW_PROJECT_NAME> worker-rustnpx wrangler generate <NEW_PROJECT_NAME> worker-rust

Sameer Ali

S

Sameer Ali•5/27/23, 5:38 PM

getting error, when i run npx wrangler@3.0.0 generate cf worker-rustnpx wrangler@3.0.0 generate cf worker-rust

Screenshot_2023-05-27_at_10.37.29_AM.png

kian

K

kianOP•5/27/23, 5:40 PM

Try experimental/worker-rust

Sameer Ali

S

Sameer Ali•5/27/23, 5:41 PM

remote: Repository not found.remote: Repository not found.

Screenshot_2023-05-27_at_10.41.24_AM.png

kian

K

kianOP•5/27/23, 5:43 PM

Lovely

kian

K

kianOP•5/27/23, 5:44 PM

Guess all of the experimental templates in the Wrangler repo don’t work with generate

James

J

James•5/27/23, 5:44 PM

You could try npm init cloudflare@1 my-project worker-rustnpm init cloudflare@1 my-project worker-rust

kian

K

kianOP•5/27/23, 5:44 PM

https://github.com/cloudflare/workers-sdk/blob/main/templates/experimental/worker-rust/

James

J

James•5/27/23, 5:45 PM

I've got an issue in around this at https://github.com/cloudflare/workers-sdk/issues/3348. C3 has broken all the old initinit commands unfortunately

sokorototo

S

sokorototo•5/28/23, 8:57 PM

Hmm, is there a way for the workerworker to use a 0.20.2 version for wasm-bindgenwasm-bindgen so we can use wasm-bindgen-futureswasm-bindgen-futures ?

sokorototo

S

sokorototo•5/28/23, 11:15 PM

Also any idea why I am getting this error?

sokorototo

S

sokorototo•5/28/23, 11:15 PM

sokorototo

S

sokorototo•5/28/23, 11:15 PM

Is it on my side? I am not using any smart pointers, no compile errors so this must be from a smart pointer

zeb

Zzeb Requests in JS can be immutable, meaning you can't get a mutable reference to th...

sokorototo

S

sokorototo•5/29/23, 10:14 AM

Ah thanks, is there a way for me to come into a mutable version. Since I don't want to copy every needed detail

spence

S

spence•5/29/23, 10:29 AM

Hi everyone, I'm having an issue with a rust worker doing some basic routing.

As an experiment I have two triggers, as follows:
https://api.example.com/*
https://api.example.com/v1/email/parse/*

And my worker has the following routes:

.post_async("/" [...]
.post_async("/text/" [...]
.get_async("/" [...]

.post_async("/" [...]
.post_async("/text/" [...]
.get_async("/" [...]

Curl has the following results:

# the following are all sent to https://api.example.com/*
curl https://api.example.com/                               # OK
curl https://api.example.com                                # OK
curl --data-binary @email.txt https://api.example.com/      # JSON of a parsed email
curl --data-binary @email.txt https://api.example.com/text/ # JSON of a parsed email

# But when I try to use https://api.example.com/v1/email/parse/*
curl https://api.example.com/v1/email/parse/                # Not Found
curl https://api.example.com/v1/email/parse                 # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse/text/ # Not Found

# the following are all sent to https://api.example.com/*
curl https://api.example.com/                               # OK
curl https://api.example.com                                # OK
curl --data-binary @email.txt https://api.example.com/      # JSON of a parsed email
curl --data-binary @email.txt https://api.example.com/text/ # JSON of a parsed email

# But when I try to use https://api.example.com/v1/email/parse/*
curl https://api.example.com/v1/email/parse/                # Not Found
curl https://api.example.com/v1/email/parse                 # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse/text/ # Not Found

Since I'm getting a Not FoundNot Found response (instead of 522), I think that indicates the issue is not with the worker platform itself, and it seems the issue is either I'm not understanding something correctly or maybe a problem with the rust routing/pattern stuff? Does anyone have any suggestions? Thank you.

sokorototo

S

sokorototo•5/30/23, 12:04 PM

Small question about Durable Objects

sokorototo

S

sokorototo•5/30/23, 12:05 PM

Say I want to make a POST call to a DO, I need to build a RequestRequest using a RequestInitRequestInit object

sokorototo

S

sokorototo•5/30/23, 12:05 PM

Small issue, I can't create a Request using a relative url like /init/init

sokorototo

S

sokorototo•5/30/23, 12:06 PM

So how do I create a Request object so that I can query the DO. Instead of using fetch_with_strfetch_with_str

sokorototo

S

sokorototo•5/30/23, 12:06 PM

Since I need to add a HTTP body?

sokorototo

S

sokorototo•5/30/23, 12:09 PM

let json = serde_json::to_string(&room_init)?;
let js_str = JsValue::from_str(&json);

let mut init = RequestInit::new();
init.with_method(Method::Put);
init.with_body(Some(js_str));

let req = Request::new_with_init("/init", &init)?;
room.fetch_with_request(req).await?;

let json = serde_json::to_string(&room_init)?;
let js_str = JsValue::from_str(&json);

let mut init = RequestInit::new();
init.with_method(Method::Put);
init.with_body(Some(js_str));

let req = Request::new_with_init("/init", &init)?;
room.fetch_with_request(req).await?;

sokorototo

S

sokorototo•5/30/23, 12:09 PM

Why doesn't this work and what am I supposed to do?

sokorototo

S

sokorototo•5/30/23, 12:18 PM

Seems I must provide a dummy http domain to make the request valid, despite the fact that I do not need one

sokorototo

S

sokorototo•5/30/23, 12:18 PM

ie Request::new_with_init("http://stub.com/init", ...)Request::new_with_init("http://stub.com/init", ...)

# the following are all sent to https://api.example.com/*
curl https://api.example.com/                               # OK
curl https://api.example.com                                # OK
curl --data-binary @email.txt https://api.example.com/      # JSON of a parsed email
curl --data-binary @email.txt https://api.example.com/text/ # JSON of a parsed email

# But when I try to use https://api.example.com/v1/email/parse/*
curl https://api.example.com/v1/email/parse/                # Not Found
curl https://api.example.com/v1/email/parse                 # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse/text/ # Not Found

# the following are all sent to https://api.example.com/*
curl https://api.example.com/                               # OK
curl https://api.example.com                                # OK
curl --data-binary @email.txt https://api.example.com/      # JSON of a parsed email
curl --data-binary @email.txt https://api.example.com/text/ # JSON of a parsed email

# But when I try to use https://api.example.com/v1/email/parse/*
curl https://api.example.com/v1/email/parse/                # Not Found
curl https://api.example.com/v1/email/parse                 # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse # Not Found
curl --data-binary @email.txt https://api.example.com/v1/email/parse/text/ # Not Found

let json = serde_json::to_string(&room_init)?;
let js_str = JsValue::from_str(&json);

let mut init = RequestInit::new();
init.with_method(Method::Put);
init.with_body(Some(js_str));

let req = Request::new_with_init("/init", &init)?;
room.fetch_with_request(req).await?;

let json = serde_json::to_string(&room_init)?;
let js_str = JsValue::from_str(&json);

let mut init = RequestInit::new();
init.with_method(Method::Put);
init.with_body(Some(js_str));

let req = Request::new_with_init("/init", &init)?;
room.fetch_with_request(req).await?;