[A-EDev]

Summary

collectGarbage looped over every seq in a range taken from other devices' acks and snapshot manifests, so a member-supplied range near 2^63 kept the worker spinning (a test ran at 106% CPU for over 3 minutes at GarbageCollection.kt:151, ignoring the JUnit timeout). It now visits only the objects this device holds in that range, and records progress exactly when the delete budget runs out.

Related issue

Change type

• Bug fix
• Feature
• Refactor or maintenance
• Build, packaging, or CI
• Documentation

Validation

• ./gradlew :app:assembleGithubDebug: not run locally, no app code outside sync2 changed; CI builds the APK
• ./gradlew --offline :app:testGithubDebugUnitTest --tests 'io.github.aedev.flow.sync2.*' --tests 'io.github.aedev.flow.sync.*': 158 sync2 and 162 sync tests, 0 failures. The new GarbageCollectionTest case finishes at once (before: spun until killed)
• ./gradlew --offline ktlintCheck: passed
• I manually tested the affected behavior on an Android device or emulator.

Test device and Android version: not device-tested

Risk and compatibility

Deletes the same objects as before for normal ranges.

• The change does not introduce secrets, private data, or unexpected telemetry.
• New user-facing text uses Android string resources.
• Dependency and lockfile changes are intentional and limited to this PR.
• Room schema changes include the required version bump and migration, or this PR does not change the Room schema.
• Breaking changes and upgrade steps are clearly documented.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.