-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brave syncer #2010
Brave syncer #2010
Conversation
00e1d5a
to
300aaa2
Compare
0b34a8b
to
47e2612
Compare
29b7ad2
to
3dc3465
Compare
48d583b
to
8c4cb39
Compare
c62cd58
to
9a9b5f7
Compare
f80b0d2
to
a8a5f2b
Compare
1. legacy order will still be sent for compatibility 2. legacy order will be used when there is no position_in_parent (legacy sync) during applying remote changes
1. Patch standardization 2. Apply clang-format
1. Remvoe weak_ptr for syncer and make sure get_record_cb_ won't get called when sync_thread is not running 2. Remove unnecessary forward declaration
1. Generate fake NIGORI entity when apply update 2. Set dummy encryption key for every update_response
sync protocol like "version" and "UniquePosition", ...etc
CI shows all green but reported aborted |
it was actually get terminated (https://staging.ci.brave.com/job/brave-browser-build-pr/job/brave-syncer/101/execution/node/425/log/) |
brave browser branch: brave-syncer
chromium: 76.0.3809.100
fix brave/brave-browser#2754
Overview:
This PR intercepts syncer's nudge/poll jobs to add brave sync records from brave/sync client.
Applying remote changes and committing local changes leverages chromium BookmarkChangeProcessor with minimal changes
Future work:
kSyncUSSBookmarks (https://www.chromium.org/developers/design-documents/sync/unified-sync-and-storage-overview)
Submitter Checklist:
npm test brave_unit_tests && npm test brave_browser_tests
) onnpm run lint
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
Reviewer Checklist: