Closed magecu closed 6 years ago
Hi there.
Can you provide me more information about your tests?
Deleted the local account created a new account and synced it with the online account.
Only a portion of the mangas were synced.
No further sync after adding or removing a manga.
Firefox version: 58.0.1
File is attached foxy-manga-reader-201824.zip
By delete local account I mean starting Firefox with "Firefox -P", then deleting the local account and creating a new clean one, without any bookmarks addons or other local settings. Then syncing with the new online account.
Yes there are quite a few fanfox/mangafox bookmarks.
I removed (or added) a manga from Foxy and then manually run the sync from firefox. Then I deleted the local account "Firefox -P" and synchronised with the online account. The removed manga was still present, like wise an added manga would not be present.
Thank you! I will run some tests to see if I can find the problem.
If there is anything else you need, just ask. I know how hard it is to reproduce a bug without enough information.
In both cases I have checked about:sync-log. No errors were reported.
Did you check about:sync-log between steps 6 and 7? Can you check it for me to see if I'm on the right track?
I found a problem with the size of the data to sync. It worked fine with my list, but I got problems when syncing your list.
1518011110160 Sync.Engine.Extension-Storage ERROR Syncing foxy-manga-reader@enakada: request failed: Error: HTTP 507; Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded (79375 > 16384 Bytes.) (resource://services-common/kinto-http-client.js:2354:21) JS Stack trace: formatResponse@kinto-http-client.js:2377:21 < processResponse@kinto-http-client.js:2352:14
Basically, it seems there is a size limit (16kb) for each object saved to the sync storage. For now, Foxy saves a single array with all bookmarks:
bookmark_list: []
I will have to redesign the storage which is a major change on how every part of the add-on works. That will take some time, because I have to make sure I won't break everyone's list during the upgrade. I will start working on that after releasing v0.5.3!
I will get you the data as soon as I can, but it might take me a couple of days, depends on how bussy I will be in the next few days. :)
No problem! I just want to confirm if there is anything else preventing you from syncing your manga. Thanks for all your help! :)
Yes you are on the right track. I also got this error, I just had to wait a little bit longer for the errors to populate, I even got the error from the original sync:
1517814518939 Sync.Engine.Extension-Storage ERROR Syncing foxy-manga-reader@enakada: request failed: Error: HTTP 507; Error: HTTP 507 Insufficient Storage: Resource access is forbidden for this user (Maximum bytes per object exceeded (22503 > 16384 Bytes.) (resource://services-common/kinto-http-client.js:2354:21) JS Stack trace: formatResponse@kinto-http-client.js:2377:21 < processResponse@kinto-http-client.js:2352:14
Sorry that it took me so long to check.
P.S.: BTW I am currently saving every so often an export of the bookmarks to a synced folder. So I am not in any danger of loosing my reading progress. :)
Yes you are on the right track. [...] Sorry that it took me so long to check.
Don't worry and thank you so much for your help! I've finished redesigning the storage and everything seems to be working as intended now. As soon as I finish testing some new features I will be releasing Foxy v0.6.0.
I will start working on that after releasing v0.5.3!
I decided to include some new features on the next release, thats why I will be skipping v0.5.3.
BTW I am currently saving every so often an export of the bookmarks to a synced folder. So I am not in any danger of loosing my reading progress. :)
Oh, thats great! I've done multiple tests after redesigning the sync storage, but it doesn't hurt to have a backup ready. :)
I had a little more time to experiment with sync and there are still some issues.
Approach 1:
Approach2:
In both cases I have checked about:sync-log. No errors were reported.