upload-progress still fired after cancel-all

[AurelienMendes]

Hi,

When I want to cancel all my on going uploads (operated with TUS plugin) I get this error :
Uncaught TypeError: Cannot read property 'progress' of undefined

After checking, this error come from (I think) the Uppy core:

this.on("upload-success", function(t, r) {
                var n = e.getFile(t.id).progress; //// here !!!!!!!!
                e.setFileState(t.id, {
                    progress: ___extends_95({}, n, {
                        uploadComplete: !0,
                        percentage: 100,
                        bytesUploaded: n.bytesTotal
                    }),
                    response: r,
                    uploadURL: r.uploadURL,
                    isPaused: !1
                }),
                e._calculateTotalProgress();
            }),

What I understand by seeing the network processes, is that when the cancel-all event is emitted the running processes are indeed cancel but new ones are created :

You can see on the capture that even if all running processes are canceled, 4 new ones are created (limit: 4 in uppy Tus option). And it is these 4 new ones that generate the errors mentioned above.

This is even more obvious when I pause all uploads before. Everything is paused, and when I click the cancel button, the existing processes are canceled, but 4 new ones are created.

Do you understand what could happen ?

Thanks

[goto-bus-stop]

yeah :/ this is a bug in our queueing code when you use a limit: N option.

[AurelienMendes]

Great ! I am reassured to learn that this is a referenced bug.

Do you already know which release will have the patch for this bug ?

[goto-bus-stop]

I've just started working on a fix for it last week, it's turning out to be quite tricky but we should be able to get it in before the end of the month.