Skip to content
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

Merged
merged 73 commits into from
Aug 20, 2019
Merged

Brave syncer #2010

merged 73 commits into from
Aug 20, 2019

Conversation

darkdh
Copy link
Member

@darkdh darkdh commented Mar 19, 2019

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:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Verified that all lint errors/warnings are resolved (npm run lint)
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

  1. Migrate sync code to Syncable Service brave-browser#2754 (comment)
  2. Unit tests

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

@darkdh darkdh self-assigned this Mar 19, 2019
@darkdh darkdh force-pushed the brave-syncer branch 5 times, most recently from 00e1d5a to 300aaa2 Compare April 4, 2019 20:30
@darkdh darkdh force-pushed the brave-syncer branch 6 times, most recently from 0b34a8b to 47e2612 Compare April 9, 2019 21:01
@darkdh darkdh force-pushed the brave-syncer branch 3 times, most recently from 29b7ad2 to 3dc3465 Compare April 16, 2019 22:55
@darkdh darkdh force-pushed the brave-syncer branch 5 times, most recently from 48d583b to 8c4cb39 Compare April 25, 2019 03:28
@darkdh darkdh force-pushed the brave-syncer branch 5 times, most recently from f80b0d2 to a8a5f2b Compare May 21, 2019 21:05
@darkdh darkdh marked this pull request as ready for review May 24, 2019 23:22
darkdh added 7 commits August 19, 2019 15:10
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
@darkdh
Copy link
Member Author

darkdh commented Aug 20, 2019

CI shows all green but reported aborted
https://staging.ci.brave.com/job/brave-browser-build-pr/job/brave-syncer/101/

@darkdh darkdh merged commit 05c7b61 into master Aug 20, 2019
@darkdh darkdh added this to the 0.71.x - Nightly milestone Aug 20, 2019
mkarolin added a commit that referenced this pull request Aug 20, 2019
@darkdh
Copy link
Member Author

darkdh commented Aug 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate sync code to Syncable Service
4 participants