Shared photos are removed and then re-added in version 2.14.2 about gphotos-sync

[gilesknap]

Hi @Phusty.

The settings you are using mean that you are completely rescanning your whole library every night. Including removing any local copies of your files that were deleted online.

That's not how I use gphotos-sync because it means that accidental deletions would get propagated to my backup. But then if you are taking snapshots of your filesystem by other means then this would be a good way to notice such deletions I guess.

Anyway. I can't comment on ever seeing this and I'm inclined to blame Google for this one. There is an outstanding bug that delivers a less items per chunk than requested, sometimes even zero, sometimes zero several times before picking up again. See the last bullet on #119. My code tries to workaround this by retrying even though zero response is supposed to mean that the search is complete.

Since it's a bug in the server and has not been fixed for 4 years I'm not holding out much hope.

Do you need to use --do-delete all the time. Could you change your workflow a little to work around this?

[Phusty]

Hi,

I was using the library with --do-delete to keep the backup aligned with the photos on Google, and I set up another script that makes a tar of a folder if something changes, notifying me on Telegram of the previous and current number of files (which is why I noticed this behavior) precisely to avoid accidental deletions from the backup.

I will try to modify the workflow in order to be sure that the backup only occurs when I have already deleted, among the latest photos taken, those that I do not want to keep.

Thank you very much for your response!

[gilesknap]

makes a tar of a folder if something changes, notifying me on Telegram of the previous and current number

Nice - in fact really the only way to use gphotos-sync as Google has crippled the API - its not a true backup but it is a good way to make sure accidental deletions are not happening.

Of course being as diligent as you are you will catch out little bugs like the one I mention in the Google API.

[gilesknap]

closing as completed