You'll notice
Useful4 Signal2
Files deleted by a cloud session are now reported as moved to trash, with paths named.
What's wrong with this entry?
Anonymous. No account, no email.
What
Deletions applied from a cloud session already went into a per-session trash folder on your machine. Now you are told, with an info line naming a few of the paths and stating plainly that the files were not erased.
Details
- The sync telemetry payload gains a
moved_to_trashcount. - Message wording: files were
moved to this session's trash on this machine, not erased.
Evidence
moved to this session's trash on this machine, not erased
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