Ignore tombstones for nonexistent items when merging bookmarks
Categories
(Firefox :: Sync, task)
Tracking
()
People
(Reporter: lina, Assigned: lina)
References
Details
Attachments
(1 file)
See bp-ad46895e-eb33-47ba-89b2-5d0480190905 for an example—the tree is pretty small (2.5k bookmarks), but there are over 1m tombstones ({"step":"merge","at":1567665986347,"took":970,"counts":[{"name":"items","count":2522},{"name":"deletes","count":1641866}]}). We'll insert entries for all of them into itemsToRemove, even if we don't actually do anything with them because they don't exist locally, and don't need to be uploaded.
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 1•5 years ago
|
||
Taking this early so we can uplift to 70.
|
|
Assignee | |
Comment 2•5 years ago
|
||
On second thought, this is going to be a pretty big patch to uplift, so letting this ride the train seems prudent.
|
|
Assignee | |
Comment 3•5 years ago
|
||
The latest version of Dogear adds completion ops for deleting local
items (to apply incoming tombstones), inserting new local tombstones
(to stage deletions for non-syncable and invalid items), and uploading
tombstones (to avoid an extra scan of moz_bookmarks_deleted).
These ops are only emitted for GUIDs that are mentioned, either as
items or tombstones, in both trees. This means we won't try to apply
tombstones for items that don't exist in Places, or upload tombstones
for items that aren't on the server.
Pushed by kcambridge@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/faabf87693c1 Use completion ops to upload synced bookmark tombstones. r=markh
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
Description
•