-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Folder structure is not maintained on device 2 #2133
Comments
Reproduced with macOS (device 0) and macOS (device 2) on
|
Device-receiver of sync data get the bookmark before it get the folder. So the bookmarks were placed in the root Device who sends to sync:
Device who receives from sync
This issue describes real steps to get the situation described in #2104 . |
The plan to fix it is:
Not quite good point - the bookmarks which are truly in the root of permanent nodes, will always have "ParentObjectId" metadata. |
so where do you plan to put the bookmark temporarily until you receive the true parent? |
@darkdh in the same place as now, either I cannot hide them because there is no way to figure out is that bookmark item the child of Will move the bookmark if the folder will arrive. If folder will not arrive, bookmark will be still where it was placed first. Nested folders can also have the issue. |
what about putting them under a new invisible[set_visible(false)] permanent node |
@darkdh The code of Or we need to update brave-core/android/ios clients to pass the additional info about is the record the direct child of permanent folder. |
If the child is under those permanent nodes, why bother putting it under Pending Bookmarks? |
because when the bookmark node arrives, I cannot understand is that a node, which arrived before parent, or the node which should be placed into some permanent folder. The sign of these two cases:
|
|
if item belongs to permanent folder, isn't its parentFolderObjectId empty? That should be sufficient to distinguish from the case that parent hasn't arrived. |
@darkdh , awesome notice, will re-check that. If parentFolderObjectId empty, will go with |
Verified passed with
Verification passed on
The folder structure is maintained after sync Verification passed on
|
Description
Folder structure is not maintained on device 2
Devices
Device 1: Ubuntu (sync chain creator)
Device 2: Windows 10 x64
Steps to Reproduce
Actual result:
Device 1:
Device 2:
Folder structure on Device 1:
Folder structure on Device 2:
Expected result:
Should maintain same folder structure
Reproduces how often:
Easy
Brave version (brave://version info)
Reproducible on current release:
Yes on beta build
Website problems only:
Additional Information
Waited for about 20 mins on device 2 folder structure didn't get resolved.
cc: @AlexeyBarabash @darkdh @brave/legacy_qa
The text was updated successfully, but these errors were encountered: