You'll notice
Useful2 Signal2
Sync tells you why a pulled file could not be written, including case- or Unicode-only clashes.
What's wrong with this entry?
Anonymous. No account, no email.
What
Failures while writing pulled files into your working copy are now reported as refusals with a reason instead of thrown as raw errors, and the summary tells apart a genuine name clash from two files differing only by letter case or Unicode form, listing the paths involved.
Details
- Recognised reasons cover a missing anchor directory, a destination that refused the write, a file landing outside the sync root, a parent path escape, a parent that is not a directory, and a path that resolves outside the sync root.
Evidence
WORKING_RESOLVES_OUTSIDE
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