A sync that runs out of time now reports as timed out rather than failed.
What's wrong with this entry?
A sync request that runs out of time now reports timed_out rather than failed, so a slow link is no longer indistinguishable from a rejected upload. Pull results can also report an outright refusal.
- The sync summary gained counters for upload timeouts, slow-but-landed uploads, and a set of deleted-file buckets.
- Stat records now carry device and inode identity, so a file replaced in place can be told apart from one edited.
- A read-only sync scope that still has unsaved paths reports them as
unsavedReadOnlyPathsand emits the telemetry eventtengu_memory_sync_ro_unsaved.
"tengu_memory_sync_ro_unsaved"
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