Cloudflare

if you have r2 access, where does it show on the dash

https://i.imgur.com/7GCSftb.png oh F then

My understanding is that that's only the case because S3 has to do an extra lookup to obtain this information.

but it also bloats the response with repetitive info (think 1000 keys) that no one ever uses, no?  even if egress is not an issue, keeping the response size down would be important over slow connections

Maybe. I'll add it to the performance backlog

<@797895289603227658> I need to investigate more, but for non-empty buckets, I'm pretty sure I'm seeing non-empty list result back. Can you confirm again that I've got the right scenario where you are just doing `await BUCKET.list()` where `BUCKET` is a binding to a non-empty bucket but the result of the list has empty `objects`.

that's right, just tested again, still no objects.  my  `compatibility_date` is `2022-04-14`, should i be updating that every morning?

No, but try moving forward to `04-18` just in case

and it looks like i need to remove `r2_public_beta_bindings` as of that date?  i'm getting an error on push

(above someone is saying that the `compatibility_flags` isn't working for them)

10021 The compatibility flag r2_public_beta_bindings became the default as of 2022-04-18 so does not need to be specified anymore.

Sometime this week everyone will be seeing that if they publish with `r2_public_beta_bindings` because it's the default and internal beta users have been notified to migrate to public beta bindings as we'll be removing that code path within the next little while

same behavior, list with no options => 0 results, list with { limit: 1 } => 1 result

unrelated, i'm getting a `413 Request Entity Too Large` putting a 3gb file in one go (with `PutObject`), is there a limit?

The limit should be 5gb but in practice ~3GB is roughly the single largest upload that'll actually work I think.

But we shouldn't be returning 413 for 3GB

the file i tried to upload is 3.01gb or something like that

and it's not a s3-formatted xml error, it's html!

That indicates it's not coming from R2. I'll raise this internally

You're doing this via the S3 endpoint at `<account id>.r2.cloudflarestorage.com` yeah?

If you're fronting via a worker your limit will be 500 MB