-
Notifications
You must be signed in to change notification settings - Fork 918
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
Fix ability to delete other device from the sync chain #11313
Conversation
const std::string guid = change->storage_key(); | ||
|
||
// Reupload local device if it was deleted from the server. | ||
+ if (bool false_as_brave_needs_skip_next_if = false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like we can follow our patching patterns here and use #define BRAVE_DEVICE_INFO_SYNC_BRIDGE_APPLY_SYNC_CHANGES_SKIP_NEXT_IF if (false)
in the chromium_src
override.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and you can also add comment in the overridden file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3bb43a4
to
2ac8203
Compare
@@ -13,8 +13,14 @@ | |||
#define RefreshLocalDeviceInfoIfNeeded \ | |||
RefreshLocalDeviceInfoIfNeeded_ChromiumImpl | |||
|
|||
// This macro disables Chromium's block which detects whether the local | |||
// device record should be re-uppload to server. We disable it because it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: re-uploaded
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't looked at the tests logic, but chromium_src
and patches
changes LGTM.
fixes brave/brave-browser#19561 This commit reverts commit https://chromium-review.googlesource.com/c/chromium/src/+/3001364 from the upstream because it breaks ability to delete other device from the sync chain
2ac8203
to
a2bc0c2
Compare
Basically this PR reverts https://chromium-review.googlesource.com/c/chromium/src/+/3001364 and updates the tests to be aware in future if Chromium will change the behavior near this place.
I had to use patch for
src/components/sync_device_info/device_info_sync_bridge.cc
.Resolves brave/brave-browser#19561
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan:
Use one from brave/brave-browser#19561