You'll notice
Useful3 Signal2
Per-turn syncing is capped by time, path count and a 64 MiB file size limit.
What's wrong with this entry?
Anonymous. No account, no email.
What
The syncer enforces published limits so a turn cannot be delayed indefinitely by file transfer. The pre-turn pull is bounded by WORKER_SYNC_BEFORE_TURN_CAP_MS at 10000 ms, dropping to WORKER_SYNC_DEGRADED_CAP_MS at 500 ms once the connection is degraded. Pushing looks at 4096 candidate paths per turn at most and refuses any file over 64 MiB, so very large files never sync.
Details
- Surplus paths beyond 4096 rotate across later turns rather than being dropped.
- At most 40 new entries are admitted per turn against a 256-entry cap, with some of that cap held in reserve.
- The published record of worker state is capped at 2 MiB, with at most 256 recorded entries and 256 recorded skips.
- If a previous worker process still holds the sync, the apply step retries up to
MAX_APPLY_ATTEMPTS(3) times withAPPLY_RESTART_DELAY_MS(5000 ms) between attempts.
Evidence
WORKER_SYNC_BEFORE_TURN_CAP_MS
Strings lifted out of the shipped bundle, so the claim above can be checked against them.