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
R2 has a non-standard requirement that all non-trailing parts of a multi-part upload be exactly the same size. With @tus/[email protected] and @tus/[email protected] 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!
The text was updated successfully, but these errors were encountered:
Similar issue was opened for tusd recently: tus/tusd#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/[email protected] and @tus/[email protected] 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!
The text was updated successfully, but these errors were encountered: