R2 has a non-standard requirement that all non-trailing parts of a multi-part upload be exactly the same size. With @tus/s3-store@1.4.3 and @tus/server@1.6.0 get the occasional error InvalidPart: All non-trailing parts must have the same length. from R2 and the multi-part upload fails.
This is definitely a shortcoming with R2 and not a bug with @tus/s3-store, but we're trying to work around the issue anyhow. Any ideas why @tus/s3-store might generate parts of varying sizes (not counting the final trailing part)?
Similar issue was opened for tusd recently: https://github.com/tus/tusd/issues/1137 My comment there also includes a tusd-specific solution, whose.cincept might be reusable for tus-node-server.
R2 has a non-standard requirement that all non-trailing parts of a multi-part upload be exactly the same size. With @tus/s3-store@1.4.3 and @tus/server@1.6.0 get the occasional error
InvalidPart: All non-trailing parts must have the same length.
from R2 and the multi-part upload fails.This is definitely a shortcoming with R2 and not a bug with @tus/s3-store, but we're trying to work around the issue anyhow. Any ideas why @tus/s3-store might generate parts of varying sizes (not counting the final trailing part)?
Thanks!