Problem with file integrity when uploaded

[bramburn]

Hello there,

I am getting an issue with the files uploaded via the API.

the Dropbox hash differ from the original and uploaded.

(venv34) Kapss-MacBook-Pro:python bramburn$ python hash_file.py /Users/bramburn/Desktop/Toc1012.fls
d2d3e87285f85ffaa8ddf0870a46bb2e580a293e32ba20a155317654479dfb2c
(venv34) Kapss-MacBook-Pro:python bramburn$ python hash_file.py /Users/bramburn/Downloads/Toc1012.fls
85b64345dbb99010eeb4e7a61bc61a99c45c595a0ba594b090b9ebad5daf8c0d
(venv34) Kapss-MacBook-Pro:python bramburn$ 

The file in /Downloads/ is the web downloaded toc1012.fls file, the file in the /Desktop/ is the original.

The file is different.

I also tried a shasum as follows with two different file and I am getting an issue with the file:

Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Downloads/Toc1008.fls 
f44df7db8f9321145a7b091fd0d25b107521d998  /Users/bramburn/Downloads/Toc1008.fls
Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Downloads/Toc1008.fls 
f44df7db8f9321145a7b091fd0d25b107521d998  /Users/bramburn/Downloads/Toc1008.fls
Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Desktop/Toc1008.fls 
ba728834eeecd6eb3dfaa5508e43815c15c07f45  /Users/bramburn/Desktop/Toc1008.fls
Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Downloads/Toc1012.fls 
4a1b522c8f5e31ed7e1d69feec5f273775b32609  /Users/bramburn/Downloads/Toc1012.fls
Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Downloads/Toc1012.fls 
4a1b522c8f5e31ed7e1d69feec5f273775b32609  /Users/bramburn/Downloads/Toc1012.fls
Kapss-MacBook-Pro:~ bramburn$ shasum /Users/bramburn/Desktop/Toc1012.fls 
5d8c75382de48bdbd25c78d20a923e869049a8a8  /Users/bramburn/Desktop/Toc1012.fls
Kapss-MacBook-Pro:~ bramburn$ 

Anyone know how to resolve this when uploading files? or making sure it is the same?

[Greg-DB]

Apologies for the delay! It looks like your post got caught in the forum's spam filter for some reason. It was just restored.

Anyway, can you share the code you're using to upload the files in this case? It sounds like something may be going wrong during the upload resulting in the incorrect data getting committed.

[bramburn]

hi Greg, i was able to resolve this. For some reason the f.tell() was off for the offset.