What
Cloud file sync keeps your machine and a cloud session's copy of the project in step. It works in passes, and each pass is started by a trigger. There is a new trigger, install_ack. A pass started this way skips the pull and the snapshot. It only republishes the session note, which is the install report.
It logs tengu_dir_sync_git_install_ack with an outcome or one of these skip reasons:
nothing_owedupload_announcedno_note_yetpeer_behind
The fallback message for a failed upload is no longer raised for these passes.
Why
The install report can now be sent on its own, without a full sync. Because these passes do not upload anything, they no longer set off the failed-upload message.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what sets off an `install_ack` pass.