You'll notice
Useful3 Signal2
Directory sync can now remove files deleted upstream, trashing them and leaving anything it is unsure about.
What's wrong with this entry?
Anonymous. No account, no email.
What
The background worker that syncs a directory gained the ability to remove files that are gone upstream, moving them to the trash rather than deleting outright, and leaving them in place when it cannot tell whether your copy changed.
Details
- New counters report deletes considered, files trashed, copies kept because they changed or because their state was unknown, mismatched deletion records, files already absent, and trashing being unavailable, refused or failed, plus retry counts per lane.
- Replacing a file can now stash a copy first and discard it if the rename succeeds; the result says whether an unstashed file was overwritten.
- No flag controlling this behaviour is visible in the changed code.
Evidence
trash_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory