drive push doesnt push certain file types twice

[DenomZero]

In a follow up to issue #237 my MD5 checksum wasn't jiving because drive push isnt pushing certain file types a 2nd time.
I use CherryTree in linux (peppermint) to make notes so it's modified regularly.
To recreate the issue with cherry tree first create a new doc and put some test data into it. Save it as sqlite unprotected file, push it, great. I leave cherry tree open this whole time. Modify the document with more test data example Tree->Insert todays node and then more test data, then save. Push the data. Looks good, because it says it worked. Check the md5 checksum with "drive md5sum | md5sum -c" and there is a conflict. Close cherry tree and force pull the data. Open your test document and the modifications are gone, therefore its not getting pushed correctly. Im sure this is why the md5 checksum wasn't jiving but I am unable to get the push to work on this file a 2nd time, I always just assumed it was just working.
Im sure I could trash the files through drive and then re-push although I havent tried it. Even a push -force doesn't work in this case -- the same md5 checksum. Normal push, -ignore-conflict, -force all react the same way.
I apologize in advance for a delay in response as I don't have the most free time.

[odeke-em]

Hello again @DenomZero, thanks for reporting this issue.
I'll try to grab CherryTree and reproduce this off my Ubuntu machine. Are you sure the changes are actually serialized and inserted into the file itself and not in an auxilliary spot? Have you tried say a cat edited_file > new_test_file && drive push new_test_file or even diffing the files? Also by default checksumming before pushes is turned off as seen in #117 because it was found to be aggressive and not necessary for the largest variety of cases. The README talks about this, but just in case you might have not seen this, you can set checksum-ing on by drive push --ignore-checksum=false ... so that in case meta data changed or some configs but not the file size and probably time this can be confirmed. I'll try this out sometime over the week.

[odeke-em]

@DenomZero would it be possible to md5sum files individually using the local shell utility after doing drive md5sum?

[odeke-em]

@DenomZero I can't reproduce your issue unfortunately.

[odeke-em]

@DenomZero could you use

$ drive push --ignore-checksum=false

also please take a look at https://github.com/odeke-em/drive#note-checksum-verification

That should sort out this problem.

[DenomZero]

Awesome. That works. Thanks for the patience and sorry for a slow responce.