Under the hood
Useful2 Signal1
Snapshot copies are hash- and timestamp-checked so a half-written file is not recorded as good.
What's wrong with this entry?
Anonymous. No account, no email.
What
Files copied into a snapshot are now checked to make sure they did not change during the copy: contents are hashed with sha256 while being read, and file size and nanosecond mtime/ctime are compared before and after. A mismatch marks the file as changed rather than recording a torn copy.
Details
- The recorded identity of a copy moved from millisecond ctime to nanosecond ctime plus an identity value.
- Refusals carry a momentary flag separating transient causes (unreadable parent directory, unclassified system error) from permanent ones.
- The old "changed while being read" refusal is gone; such a file is now returned as changed instead.
- Case-insensitive or Unicode-normalization collisions between two changed paths are refused with their own message.
- Optional before-open and after-read hooks were added to the staging options.
Evidence
collides with another changed path that differs only in case or normalization
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.233
Checkpoint notice now tells you how to undo the turn
Both mention checkpoint
-
v2.1.233
Resume checkpoint file now tells you how to undo the turn
Both mention checkpoint