One of the queries that Synology makes
One of the queries that Synology makes results in a
NextMarker
loop - forever31 Replies
Is it making the same request over and over? Like, with the same delimiter/prefix/marker?
Yep
R2 returns a
Marker
of foo
and a NextMarker
of foo
so it keeps following NextMarker
I'm going to move the files from my R2 bucket onto S3 & run the same request against S3
Specifically it's <NextMarker>Resilience_1.hbk/</NextMarker>
(varies between upload jobs but you get the idea)
Previously the job uploaded to a folder called sdk-example
and it looped on this
It's basically being told 'to check this folder, use this marker' but that marker isn't progressing anything
so
NextMarker
is Resilience_1.hbk/
so I'll add the marker
search param with that value
now I'm stuck forever, since it's just telling me to check where I already am
if I remove the delimiter and the marker, we can see there are files

including other folders after that

if I do the same against S3:
Let me try and setup a repro that doesn't involve Synology
Repro:
S3:
R2:
Both ran on empty buckets


Same file/folder path on both
To clarify why
Marker: "folder/"
is used, that's what R2 returns as NextMarker
if I omit the marker.I somewhat vaguely remember seeing an issue like this on our issue tracker
But it might have been something completely different
Okay but this is suuuper helpful, I can now write a test to see what happens

Let's just say Synology will, uh... 

Good thing you have R2_NOCOST right

Yes - but we're also within free 

@kiannh is great, yeah
If you want I can keep going π
This varies as itβs the base folder name, which defaults to the NAS name with the hbk extension. You can select it.
I should apply as QA /s
Glad this was got to the bottom of! Thanks so much for the debug yβall. Would love to use R2 with my synology at some point π
Yeah I haven't dug into this yet, but if it is something simple on our end, expect a fix soon. Otherwise I might procrastinate, but I'll report back here what I find
I have my job ready, if you need a test just ping me anytime. Itβs a very easy click to test, and even if I need to set-it up again I did a separate token, so I roll and restart easily.
It was fun, seeing @kiannh swear at Signatures in S3 CLI π

Any news here? π Is there a better place I could file this for tracking? Ticket to custesc maybe?
Yeah a CUSTESC is probably going to the best course of action, I havenβt found time to look into this yet π¦
Alrighty, will do π
Should we do one and CC the other into it? π
can do. I was gonna take a look this weekend, don't have much time this week. Will DM you beforehand in case you've already done one 

Not sure Iβm gonna find the time, as it requires a bunch of info to share and to prepare π
@sdnts so, we should CUSTESC it, right? No progress in the meantime?
Hey, yeah that sounds right. I've been OOO for the last couple of weeks, so no progress yet unfortunately
Hopefully gonna do that today, finally...