You'll notice
Useful3 Signal1
Files skipped by cloud sync for being too large are now named, up to five paths.
What's wrong with this entry?
Anonymous. No account, no email.
What
Cloud directory sync now warns when individual files are skipped for being over the size limit, naming up to five paths, instead of dropping them silently. The size limit is filled in at runtime.
Details
- Oversize files are tracked in their own bucket, separate from the other reasons a file is held back.
- The message ends with the fragment
MiB each), so changes to them stay on this machine:. - Related: the internal "uploads not taken" lines dropped from info level to debug, so they no longer appear in the normal log stream.
Evidence
MiB each), so changes to them stay on this machine:
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