Under the hood
Useful2 Signal2
Skipped files during sync now record whether the cause was momentary and worth retrying.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a file is skipped during a sync, the result now records whether the cause was momentary. Transient causes (the file changed while being read, an unrecognised system error) are marked retryable; structural ones (not a regular file, resolved outside its directory) are not.
Evidence
why: "resolved outside its directory"
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