Getting a very vague error trying to complete multipart uploads in a worker:

completeMultipartUpload: There was a problem with the multipart upload. (10048)

. Any ideas? I am passing all the parts.

Can someone point me to a step by step guide on how to mock R2 for local development? I have no idea what I am doing here Tried using wrangler in local mode

npx wrangler pages dev --persist-to wrangler-local-state/ --local -- npm start

created

wrangler-local-state/r2/bucket_name

and added a binding to

.toml

but fetching a key from R2 is still returning null

Same thing here. I cannot find nice examples to set up locally and then replicate it online

--r2=BUCKET

is needed too

Or well, is preferred -

pages dev

shouldn't read from

wrangler.toml

if it is

That one isn’t documented lol

nothing new there :^)

so if my .toml file is

r2_buckets  = [
  { binding = "FEATHERS", bucket_name = "feathers", preview_bucket_name = "feathers-preview"}
]

Do I need

--r2==FEATHERS

or

--r2==feathers

?

--r2=FEATHERS

or --r2 FEATHERS, it's not fussy

Alright, thanks guys!!

Local development uses local storage. It cannot access data stored on Cloudflare’s servers. By default, data in local development is not persisted. This means if you write a value into KV, for example, the next time you start local dev, it will no longer exist. Enable persistence with the --persist flag.

anyway to bind to the cloudflare servers?

Remote data will be used if you use

wrangler dev

in remote mode (the default)

You can specify preview buckets/namespaces in your

wrangler.toml

file

and/or via https://developers.cloudflare.com/pages/platform/functions/bindings/#r2-buckets

wrangler dev is great! Is there an alternative to it for a pages project that will also work in remote mode?

It doesn't work for me. Anyhow, why do you need

--persist-to wrangler-local-state

when

--persist

already creates the folder

.wrangler\state

. My issue is that I can create an object in

.wrangler\state\R2 ..

using just the

--persist

flag, but I cannot read it!

Unfortunately not,

wrangler pages dev

only supports local mode at the moment

also not possible to run pages in "production" mode or something right?

Not without publishing, no

Because it requires you to upload all of your assets, you might as well be deploying it

Ok. Got it 🙂

Just following up on this, I've observed it working when I try smaller files that only take 1-3 parts, but larger ones (19 parts) fail when trying to complete. Is there a limit I'm not aware of? The larger file is 183MB.

Are all your parts the same size (except the last one, which may be smaller)?

The limit for file sizes in multipart uploads is 5TB, and individual parts should be >5MB

Oo that might be the issue. The smaller files are getting chunked evenly but the larger seems to be sending very slightly different sizes.

Hi, Could anyone explain how to configure R2 to work locally? Do we need the

--persist-to wrangler-local-state

? why

--persist

is not enough (like for KV) ? With KV I have not issues writing and reading locally, but with R2 I cannot read, I always get an empty body

We want to host a .json file for each user of our application in R2. However the loading time is very bad: 150-300ms (first load 500+ms) just to load the file directly in the browser (we tested it from multiple locations). If we host the same File for example in Shopify Assets (Shopify CDN) its only 30-80ms. Does R2 not have CDN? Do we have to activate it separately? The R2 domain is proxied via cloudflare DNS