Aaron Lehmann 2074688be9 Fix S3 multipart upload pagination loop condition ... The loop that iterates over paginated lists of S3 multipart upload parts appears to be using the wrong variable in its loop condition. Nothing inside the loop affects the value of `resp.IsTruncated`, so this loop will either be wrongly skipped or loop forever. It looks like this is a regression caused by commit 7736319f2e. The return value of `ListMultipartUploads` used to be assigned to a variable named `resp`, but it was renamed to `partsList` without updating the for loop condition. I believe this is causing an error we're seeing with large layer uploads at commit time: upload resumed at wrong offset: 5242880000 != 5815706782 Missing parts of the multipart S3 upload would cause an incorrect size calculation in `newWriter`. Signed-off-by: Aaron Lehmann <alehmann@netflix.com>		2023-02-21 20:57:50 -08:00
..
api	Fuzzing: Rewrite existing fuzzers to native go fuzzers	2022-11-12 17:30:10 +00:00
auth	replace strings.Split(N) for strings.Cut() or alternatives	2022-11-10 22:38:12 +01:00
client	Merge pull request #3788 from thaJeztah/deprecate_ReadSeekCloser	2022-11-18 08:53:15 +00:00
handlers	Log username on successful requests	2023-01-30 09:32:39 -08:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	format code with gofumpt	2022-11-03 22:48:20 +01:00
proxy	Merge pull request #3787 from thaJeztah/simplify_mocks	2022-11-18 08:53:26 +00:00
storage	Fix S3 multipart upload pagination loop condition	2023-02-21 20:57:50 -08:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	Merge pull request #3772 from thaJeztah/registry_logging_simplify	2022-11-08 09:17:20 +01:00
registry_test.go	replace deprecated io/ioutil	2022-11-04 23:47:52 +01:00
root.go	format code with gofumpt	2022-11-03 22:48:20 +01:00