fix: keep legacy sync migration complete after playback-speed cleanup - #11
Conversation
|
Warning Review limit reachedNext included review available in 44 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe deprecated ChangesLegacy encrypted migration
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to Clients may delete the deprecated playbackSpeeds collection without being prompted to repeat encrypted migration; the collection remains supported for legacy reads and its limits remain unchanged. The covered behavior is ready to merge. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deleting a migrated
playbackSpeedscollection can restart legacy migration. Allow clients that have successfully synced playback speeds intosettingsto acknowledge that throughGET /v1/encrypted_sync?playback_speeds_in_settings=true; those requests no longer require the deprecated collection for completion.Default requests preserve the previous completion rule. This protects older clients and interrupted migrations, including accounts with unrelated encrypted settings but speeds still only in the original document. Existing collection GET/PUT and legacy document reads remain available. Older clients may still recreate a deleted collection through their existing migration behavior.
The HTTP regression covers interrupted uploads, unrelated settings, old-client default requests, explicit acknowledgment after migration, deletion, and continued legacy endpoint access. All 57 server tests and Rust formatting checks pass. No database migration is added.
Companion client PR: OpenTubeX/OpenTubeX#1151
Implemented with GPT-6 through Codex.