feat(upload): plannedFileCount from backup engine; cap 1M #1535
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/upload-planned-count"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Android backup runs created upload sessions without
plannedFileCount, so the activity feed's receive progress fell back to a growing received-count denominator — the X/X-grows-on-both-sides bug. Now the backup engine threadsreconciled.pending.sizethrough session creation (clamped to the new server cap), giving every run a stable at-start denominator.Changes
BackupEngine: pending count →openOrRecoverBatch→createBatch→UploadSessionClient.createSession(plannedFileCount); clampMAX_PLANNED_FILE_COUNT = 1_000_000UploadSessionService:validatePlannedFileCountcap 100_000 → 1_000_000 (real runs exceed 100k; ~300k observed)Tests