Uppy: Uploading many files through AWSS3 plugin issues

[ogtfaber]

Referencing this issue: https://github.com/transloadit/uppy/issues/468

The limit-option really helps during the upload progress making it more easy on the browser, however, there are many issues left regarding uploading many files at once:

• [x] The Statusbar upload speeds, time remaining, # of MB's, are incorrect when applying the "limit" option (i'm using a limit of 3, so Uppy uploads only 3 files at the same time)
• [x] Using the AWSS3 plugin, "preparing for upload" (gathering signed upload URLs) can take a while and has the same problems the uploader faces without using the "limit" flag. It should 'batch' the requests to ask for signed urls, instead of throwing them all out at once, which increases the chances these requests fail
• [x] While Uppy is "preparing for upload", there is a clickable "Upload" button in the Statusbar, which when clicked basically restarts the process from scratch (bug)
• [x] While the files are being "dropped" in the dropzone, it can take a long time before they're ready to be uploaded, especially on slightly older machines. The upload button is already active, but when you click it it's actually still populating the files.

Happy to help, but just wanted to make a note of these issues.

[goto-bus-stop]

Just wanna acknowledge these issues & thanks for writing them down!

I think the first point happens because we don't initialise the file.progress object with the file size until the upload has actually started—it may be fixed by setting the bytesTotal and bytesUploaded properties in Core's upload-started event handler
I'm on mobile so I'll check out the rest later 😅

[goto-bus-stop]

The Statusbar upload speeds, time remaining, # of MB's, are incorrect when applying the "limit" option (i'm using a limit of 3, so Uppy uploads only 3 files at the same time)

This should be addressed by #526. Still needs some testing but first I'm getting lunch :)

While Uppy is "preparing for upload", there is a clickable "Upload" button in the Statusbar, which when clicked basically restarts the process from scratch (bug)

This should be addressed by #524

[goto-bus-stop]

While the files are being "dropped" in the dropzone, it can take a long time before they're ready to be uploaded, especially on slightly older machines. The upload button is already active, but when you click it it's actually still populating the files.

We talked about this in the context of programmatic use before but didn't get to a proper conclusion in https://github.com/transloadit/uppy/issues/249 and https://github.com/transloadit/uppy/pull/294. It's a good point that this can also happen in the UI, and makes it a bit more pressing since you can't easily work around it there. maybe we should revive #294.

[goto-bus-stop]

While the files are being "dropped" in the dropzone, it can take a long time before they're ready to be uploaded, especially on slightly older machines. The upload button is already active, but when you click it it's actually still populating the files.

This was finally addressed in #294 and released in 0.24; we now no longer read the files to detect their type before adding them. Thanks!