S3 and R2 still differ in V2

Is this test case still in place? https://discord.com/channels/595317990191398933/940663374377783388/984897656851685476 R2's current behaviour should fail that.

It's the exact same issue that broke Hyper Backup in June at a glance haha

Hey I'm getting

ECONNRESET

when fetching cloudflare storage files with presigned URL with VPN (cloudflare is blocked, so VPN is necessary), the issue detail [here in github](https://github.com/perspect3vism/ad4m/issues/240). I have tried switch http client library in NodeJS, but still no lucky, anyone seeing similar issues or have any context?

does anyone know how to connect to r2 with cyberduck?

I've added the r2 profile, but whenever I select it it changes the address to amazon

Huh, this test still does exist...

Either that or the dashboard is silently ignoring an empty folder

Lemme try with an SDK

Ugh, it might actually be the dash, I'll wait to see what you find out

If that is the case then I wouldn't expect it to be an issue (for Synology) - but it did break it before

Let's see

I honestly hoped it was this... sort of bad, but an easy fix.

Seems to work fine with aws-sdk-js-v3

Welp

Are you selecting R2 as the connection type in the dropdown (I had to restart Cyberduck after installing the profile to get it to show up in that list) The URL you use should be

<bucket>.<account>.r2.cloudflarestorage.com

. I just tried it and it seems to be working

@Sid | R2 turned out it was doing some automatic detection based on the uri entered and I needed to paste it in without the

https

otherwise it would insist I was trying to add webdav

Oh, so just to clarify, everything's cool but the dash just doesn't show the empty object, right?

unfortunately I'm still not able to connect though

The dashboard doesn't seem to upload it at all

which then of course means it won't show

Well that's convenient because I'm already debugging issues with uploading objects on the dash

S3

js
  Contents: [
    {
      Key: 'folder/empty/',
      LastModified: 2023-02-20T15:19:14.000Z,
      ETag: '"d41d8cd98f00b204e9800998ecf8427e"',
      ChecksumAlgorithm: undefined,
      Size: 0,
      StorageClass: 'STANDARD',
      Owner: [Object]
    }
  ],
  Delimiter: '/',
  IsTruncated: false,
  Marker: '',
  MaxKeys: 1000,
  Name: 'sdk-example-kian',
  Prefix: 'folder/empty/'

R2

js
  Contents: [
    {
      Key: 'folder/empty/',
      LastModified: 2023-02-20T15:17:45.119Z,
      ETag: '"d41d8cd98f00b204e9800998ecf8427e"',
      ChecksumAlgorithm: undefined,
      Size: 0,
      StorageClass: 'STANDARD',
      Owner: [Object]
    }
  ],
  Delimiter: '/',
  IsTruncated: false,
  MaxKeys: 1000,
  Name: 'sdk-example',
  NextMarker: 'folder/empty/',
  Prefix: 'folder/empty/'

Everything looks good to me - but R2 provides

NextMarker

when

IsTruncated

is

false

@Sid | R2 aha, it's working now! the url wasn't supposed to have my bucket path at the end

Oh

Maybe this is it?

Maybe it looks for

NextMarker

rather than checking

IsTruncated

& now loops infinitely waiting for that to be

null