Apply one SyncEvent from the SDK's synchronize() stream to the running
counters and emit the corresponding log line. The action's syncCommand
calls this in a loop; the function is exported (and the SyncEventCounters
type with it) so tests can exercise every event variant independently,
including the copy-* events that require b2-to-b2 sync to fire from the
real engine.
Informational lifecycle events (upload-start, compare, etc.) are
deliberate no-ops; listing them explicitly keeps the switch exhaustive
so TypeScript errors if the SDK adds a new variant.
Apply one
SyncEventfrom the SDK'ssynchronize()stream to the running counters and emit the corresponding log line. The action'ssyncCommandcalls this in a loop; the function is exported (and the SyncEventCounters type with it) so tests can exercise every event variant independently, including thecopy-*events that require b2-to-b2 sync to fire from the real engine.Informational lifecycle events (
upload-start,compare, etc.) are deliberate no-ops; listing them explicitly keeps the switch exhaustive so TypeScript errors if the SDK adds a new variant.