Join GitHub today
A file deleted from all nodes may exist in the "out of sync" list #4627
When a file is deleted from the slave first, and then from the read-only master. It disappeared and later existed again in the "out of sync" list on the master. I feel it should be excluded permanently in the list.
My steps to reproduce:
I tried to restart Syncthing or the operation system, but the problem persisted
Screenshots from the master:
Syncthing Version: v0.14.42
Master: Windows7 (64-bit) Slave: Android 7.1
I know that the state of out of sync is expected in this case. 2 is deleted from the slave and the master so it no longer exists, should it still exist in the out of sync list? Also it seems inconsistent that 2 is excluded in the count of global and local state but included in the out of sync list.
If this scenario is unexpected, then this is a bug report. Otherwise, this is a feature request because an updated list may be useful when solving the out of sync.
No, it’s a bug. What should logically happen I think is
It’s similar to the other issue when a new device with identical contents coming online will make a send only device fully out of sync.
We should resolve the differences as long as it doesn’t result in differences on disk for the send only folder.
Currently we have to press override now and then just for internal metadata reasons, which is ugly.
From what I remember, I did try ...
.. and I think at that point I did mess up something. As this resulted in Syncthing keeping the missing files as "unsynced" state. Which is quite obvious, as the source wasn't present anymore and the marked files for deletion weren't there either.