-
Notifications
You must be signed in to change notification settings - Fork 80
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
GIF and Video files are not deleted once they have been uploaded #25
Comments
GIF & Videos are not deleted because the methods that checks uploaded and local file are the same are broken: |
Trying to fix this bug I've realised that it's very difficult and expensive that to files are the same before deleting the local one. The original code was doing different things depending the media type: gif, video and image
One alternative came to my mind to simplify and fix the problem 💡 : Compare hashes of the downloaded file and the local one. I don't like to download the image 🗑️, it seems a lot of time/bandwidth wasted (let's imagine to do the same for videos). But unfortunately the hash of the downloaded file is different from the local one 😮, this is due to Google Photos metadata, EXIF stripping, image & video processing... So this alternative is not doable 😞 A less secure, but acceptable IMO way to check the file was properly uploaded could be rely on the Google Photos response. If Google says that the item was properly uploaded, we would remove it from local storage. And I'm thinking 🤔 if this NOTE: I'm going to disable this option because it's not complete and it's broken for several formats, as I mentioned above. |
Just discovered your tool (very useful for my use case) and would need to use this 'deleteAfterUpload' feature. |
I want to use it, please rely on google's API response. |
I'm returning from holidays, and this is gonna be my first issue to work on... |
Fix issue #25 - Enable object deletion after successful upload
GIF files are uploaded but never deleted from local disk
The text was updated successfully, but these errors were encountered: