You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: keep a full local discovery request across a running sync
slotNextSyncFullLocalDiscovery() is documented to ensure the next sync performs
a full local discovery, but it only invalidated _timeSinceLastFullLocalDiscovery.
A sync that was already running restarts that timer when it finishes, so a
request arriving mid-sync -- the common case, since the watcher emits
lostChanges() precisely while changes are pouring in -- was silently dropped and
the next sync read from the database instead. The missed changes then waited for
the periodic full local discovery, an hour by default, or forever where that
interval is configured negative.
Track whether a request arrived after the running sync fixed its discovery
style, and only mark a full local discovery as done when none did.
While here, check the selective sync list in warnOnNewExcludedItem() before
stat()ing the file: the function runs once per added file and the list is empty
unless the user configured selective sync.
Signed-off-by: Felipe Tumonis <ftumonis@gmail.com>
0 commit comments