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
It seems like the second last chunk is often more than resumableChunkSize bytes. It seems like the data that should be in the second last chunk and the last chunk are concatenated into the second last chunk, and the last one is sent as well.
If i just put all the pieces together without taking this into account, I will end up with a file bigger then the one i sent (the data in the last chunk is replicated once in the end).
This seems like a bug. Either the last chunk should never be sent, or (more reasonable) the second last chunk should be of size resumableChunkSize.
I am using the latest from the master branch, and resumableChunkSize = 512 * 1024. I get this bug with all tested files with sizes above resumableChunkSize.
The text was updated successfully, but these errors were encountered:
Using forceChunkSize: true fixes the size of the second last chunk, but with this option disabled the last chunk is sent even though the data in it is already sent in the second last chunk.
It seems like the second last chunk is often more than resumableChunkSize bytes. It seems like the data that should be in the second last chunk and the last chunk are concatenated into the second last chunk, and the last one is sent as well.
If i just put all the pieces together without taking this into account, I will end up with a file bigger then the one i sent (the data in the last chunk is replicated once in the end).
This seems like a bug. Either the last chunk should never be sent, or (more reasonable) the second last chunk should be of size resumableChunkSize.
I am using the latest from the master branch, and resumableChunkSize = 512 * 1024. I get this bug with all tested files with sizes above resumableChunkSize.
The text was updated successfully, but these errors were encountered: