Cloud checkouts could fast-forward from a downloaded git bundle, but no caller enables it.
Overlay bundle download, verify and fast-forward merge are complete behind an option defaulting to false.
What's wrong with this entry?
The sync manifest can now carry an overlay block (hash, size, target head, pin) pointing at a git bundle. The worker downloads it, verifies it, fetches it and does a fast-forward-only merge. It is behind the same overlay option that defaults to false, and no caller in this build passes true.
- The bundle must be a version 2 git bundle whose prerequisite commits exist locally; if the clone is shallow, sync fetches
--depth=1from origin first. - Refs land under
refs/ccr-seed/overlaybefore the merge. - The apply refuses on a detached HEAD, a dirty working tree, a target head that is not a descendant of the current one, or if a turn has already started.
- Reported as
tengu_dir_sync_overlay_start,_completeand_failed, plusccr_dir_sync_overlay.
# v2 git bundle
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