Hi, just started with Rust/Workers, it seems that `npm init cloudflare my-project worker-rust` doesn

RrianXMS Hi, just started with Rust/Workers, it seems that `npm init cloudflare my-projec...

J

James•5/25/23, 9:18 PM

These commands changed a bit in wrangler v3. You can try

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust for now.

J

James•5/25/23, 9:22 PM

I've created https://github.com/cloudflare/workers-sdk/issues/3348. cc @admah @penalosa

JJames These commands changed a bit in wrangler v3. You can try `npm init cloudflare@1 ...

R

rianXMSOP•5/25/23, 9:23 PM

Alright, thank you very much.

S

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

Hey, I'm new here

S

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

Small question why aren't the handlers registered to Router not closures but function pointers?

S

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

An

impl FnOnce

impl FnOnce

impl FnOnce

impl FnOnce would have worked swimmingly there don't y'all think?

K

kian•5/25/23, 9:37 PM

Are you running into issues with how it is now?

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

S

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

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

S

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

Seems like an easy quality of life improvement

S

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

Now I can't use the nice Router

S

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

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

K

kian•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

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

S

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

But what if i want to capture variables

Ssirupsen Put them in `with_data`

S

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

Ah, I see

K

kian•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

K

kian•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

K

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

K

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

Try

npx wrangler generate <NEW_PROJECT_NAME> worker-rust

npx wrangler generate <NEW_PROJECT_NAME> worker-rust

npx wrangler generate <NEW_PROJECT_NAME> worker-rust

npx wrangler generate <NEW_PROJECT_NAME> worker-rust

S

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

getting error, when i run

npx wrangler@3.0.0 generate cf  worker-rust

npx wrangler@3.0.0 generate cf worker-rust

npx wrangler@3.0.0 generate cf  worker-rust

npx wrangler@3.0.0 generate cf worker-rust

Screenshot_2023-05-27_at_10.37.29_AM.png

K

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

Try experimental/worker-rust

S

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

remote: Repository not found.

remote: Repository not found.

remote: Repository not found.

remote: Repository not found.

Screenshot_2023-05-27_at_10.41.24_AM.png

K

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

Lovely

K

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

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

J

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

You could try

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust

npm init cloudflare@1 my-project worker-rust

K

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

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

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

init

init

commands unfortunately

S

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

Hmm, is there a way for the

worker

worker

worker

worker to use a

0.2

0.2

0.2

0.2 version for

wasm-bindgen

wasm-bindgen

wasm-bindgen

wasm-bindgen so we can use

wasm-bindgen-futures

wasm-bindgen-futures

wasm-bindgen-futures

wasm-bindgen-futures ?

S

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

Also any idea why I am getting this error?

S

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

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

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

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

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("/" [...]

.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

# 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 Found

Not Found

Not Found

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

S

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

Small question about Durable Objects

S

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

Say I want to make a POST call to a DO, I need to build a

Request

Request

Request

Request using a

RequestInit

RequestInit

RequestInit

RequestInit object

Hi, just started with Rust/Workers, it seems that `npm init cloudflare my-project worker-rust` doesn

Similar Threads

Similar Threads

Similar Threads