Under the hood
Useful1 Signal1
Sync failure reporting splits "could not send" from genuinely unreadable content.
What's wrong with this entry?
Anonymous. No account, no email.
What
Sync feature reporting no longer lumps failures under a single "unavailable" label. An internal error now reports as could_not_send, and a give-up state reports as unreadable only when the underlying cause was a read failure, otherwise could_not_send.
Evidence
reason: P.gaveUp === "read_failed" ? "unreadable" : "could_not_send"
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