Synced objects now use full paths and always publish through one client.
What's wrong with this entry?
Synced objects are now identified by a full directory-plus-suffix path rather than a bare name, and outbound publishing always goes through the direct client with a worker-side marker and optional stall and restart-pause timings. The older fallbacks (size-threshold direct upload, an over-cap row write, and an etag memo on rejected requests) are gone from this path.
a sync object is named by a lowercase-hex sha256
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