Under the hood
Useful1 Signal3
Directory sync reporting now names the engine used and adds six git-engine events; syncing itself is unchanged.
What's wrong with this entry?
Anonymous. No account, no email.
What
Directory sync push and pull events now record which engine ran and git-specific counters, and six new events cover the git engine's lifecycle. This is reporting only; nothing about syncing changes.
Details
- New counters include bundle size in bytes, commit count, prerequisites, withdrawn installs, held-back deletes, parked overflow and skipped rounds.
- New events: git open (carrying the branch fast-forward rule and whether an upload happens at open), fast forward, peer silent, uploads not taken, unreachable, and reachable again.
Evidence
tengu_dir_sync_git_uploads_not_taken
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