Closed janklimo closed 3 years ago
If I understand correctly, this is ultimately a bug in Uppy? I'm not sure how I feel about working around an issue that should be solved elsewhere. Even Uppy's official API backend for multipart S3 uploads has the same issue, right?
This seems like something that should just return a 404 vs raising an error. Even if it wasn't an issue in Uppy, what if an actual key was passed and in, but it was deleted elsewhere.
That sounds reasonable to me. Would you like to submit a pull request?
Released 1.1.0 with changes in https://github.com/janko/uppy-s3_multipart/pull/21.
As explained in this issue, Uppy will try to abort multipart uploads with key of value
null
when you abort too fast.Steps:
@janko do you think we should handle that in this gem? We see quite a few of these in production so I'd like to contribute a fix.