You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am investigating slowness around publishing new snapshots to s3. I turned on debugging and the ListObjects call appeared to double up on the prefix ie GET /?max-keys=1000&prefix={prefix}%2F{prefix}%2F.
As far as I can tell I have the s3 endpoint configured correctly and I am not sending a prefix in the command but do have the prefix configured in the endpoint.
Original PR: #621Fixes: #619
I've added unit-test to Martyn's PR.
Without this fix, if `prefix` is set on S3 publish endpoint,
aptly would incorrectly build path cache and re-upload every object
on publish.
I am investigating slowness around publishing new snapshots to s3. I turned on debugging and the ListObjects call appeared to double up on the prefix ie
GET /?max-keys=1000&prefix={prefix}%2F{prefix}%2F
.As far as I can tell I have the s3 endpoint configured correctly and I am not sending a prefix in the command but do have the prefix configured in the endpoint.
Unless I am reading the code incorrectly it looks like that is happening as a result of these 2 lines:
https://github.com/smira/aptly/blob/master/s3/public.go#L270
https://github.com/smira/aptly/blob/master/s3/public.go#L325
The text was updated successfully, but these errors were encountered: