Group of 2 You'll notice
Directory sync now ships changes mid-turn and tracks whether an uploaded generation has been acknowledged
What
The directory-sync engine, which keeps a cloud/remote session's checkout in step with changes on the user's machine, was substantially restructured:
- A new handler tracks whether a generation is "owed" (uploaded but not yet acknowledged or refused by the sync service), and notifies the user distinctly for a "refused" case versus a "not taken" case.
- Progress past a "not_published" state now only proceeds at defined turn boundaries (
turn_end/turn). - Snapshotting and shipping changes is now parameterized by a "point" in the turn, including
turn_endandbefore_command, tracked via a newmidTurnShipconcept, so changes can ship partway through a turn rather than only at the end. - The worker's returned interface now exposes a
streamingfield wired to a change feed, started as part of the worker setup.
Why
This makes directory sync more responsive, shipping changes at more points during a turn instead of waiting until the end, while giving the user clearer feedback when an upload is refused versus simply not yet taken.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The exact trigger conditions for mid-turn shipping and what consumes the streaming change feed are not stated.