New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File checksum not matching after uploading with XHR #4948
Comments
Do you have more information about the changes you see on those files? Does it happen for any file or only some of them? Does it reproduce consistently, or is there some condition? Could you also share the version of the Uppy packages you are using to help us reproduce the issue. |
Hi @aduh95 The file sizes and names are not changed. But, if I try to read the file, it gives an error. So, I tried verifying the checksum for the file before and after uploading, and they donot match for those specific files. Thank you |
Hum OK interesting. If the file size is the expected one, my hunch would be that the data might be written out-of-order. Any chance you could try uploading a big ASCII text file and share the result with us so we can validate that hypothesis? The following command should generate a roughly 1GiB file: node -e 'for(let i=0; i < 1e8; i++) console.log(i)' > myBigTextFile.txt Because it's ASCII, it should be much easier to understand what's happening. |
It would probably help to upgrade as well. You're years behind the latest version. |
Initial checklist
Link to runnable example
No response
Steps to reproduce
I am uploading a bunch of tiff and netcdf files using XHRUpload with Uppy. Code looks like this:
Expected behavior
The files are uploaded and I can see them in the server. They are of the same size. The expectation is that the uploaded file checksum should also match with the checksum in the local directory.
Actual behavior
The checksum doesn't match for some of the files that are uploaded. If I upload a single file of size >500MB, the checksum doesn't match either. Any idea on what might be the issue here?
The text was updated successfully, but these errors were encountered: