Path checks for directory sync go through the storage backend, and the mismatch warning wording is shared.
What's wrong with this entry?
Checks on paths owned by directory sync now classify a path as real, absent, redirected or not-a-directory through the storage backend when that backend is active, falling back to walking the path with lstat otherwise. The message you see when a session's sync was set up from a different directory now comes from a single shared helper on both paths.
- Probe failures now have distinct codes, and a classifier for a vanished source produces codes such as
batch_dir_vanishedandsource_unverifiable_parent_link. - Whether the backend path or the lstat fallback runs is decided by an internal storage-backend check that is not named in the surrounding code.
sync-owned path probe: unexpected answer
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