Merlijn Vos

> Not required for Uppy 3.0, correct? Not unless we want to postpone the release by two weeks (has to be tested thoroughly). It's a breaking change unfortunately.

Hi, size is not always returned by the providers so that's is not something we can do much about unfortunately. Regarding the second error, that seems to be something different....

@netdown can you still reproduce on latest as @mifi explained?

Uppy and companion instances are 'married' to each other, meaning you can't do a multi instance setup with picking up the upload later in a different companion instance. Companion isn't...

Can we turn this issue into something actionable so we work towards closing it? What needs to happen? Code changes? Docs?

Perhaps we can quickly test it first ourselves and see if it works. If we decide to support it there should be a test for it in my opinion. But...

But AFAIK two people here already tested it and it didn't work with redis enabled so I suppose we can go straight into deciding whether we want to support this?

Can you help me understand if this would solve a problem? You still need to upload the same amount of total chunks regardless of order.

Alright! I'm still wondering if it would be best to make this the new default, or that the current approach can have benefits in some scenarios.

@arturi is `relativePath` always present in `meta` or is it dynamic?