mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #200] Index out of bounds while trying to sync from/to NC 14 w/ bookmarks App 0.14 #191
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#191
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tkurbad on GitHub (Nov 24, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/200
Software versions
Steps to reproduce
Expected outcome
Sync should progress to the end. Additional server bookmarks should appear locally in browser, additional local bookmarks should be stored on server.
Actual outcome
Sync fails after a while with the error message "Index out of bounds" (sometimes printed several times).
Not checking "reset cache" doesn't make a difference. (Only sync takes longer and there are at least 20 "Index out of bounds" errors shown at once in the end).
@tkurbad commented on GitHub (Nov 24, 2018):
Debug log: https://gist.github.com/tkurbad/0eb1763328e67a9924ec1a44964b8ebe
It seems to always fail in the same place.
@marcelklehr commented on GitHub (Nov 24, 2018):
Thank you for the detailed report. The error may present due to a recent change I made to increase performance. I've just released a bugfix release. Could you try it again once you've received the update?
@tkurbad commented on GitHub (Nov 25, 2018):
Thank you for the fast response.
The error just appeared again. However, sync automatically restarted, so I'll give it a (few) runs more and will update my findings...
@tkurbad commented on GitHub (Nov 25, 2018):
Okay, I now got "Index out of bounds" and "QUOTA_BYTES quota exceeded" (at the same time). :-(
EDIT: Syncing starts anew after each "Index out of bounds" and then fails at another place with the same error.
@marcelklehr commented on GitHub (Nov 25, 2018):
The quota bytes error is probably due to the log being too full :/
You can
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "consoletabchrome.storage.local.set({'log': []})and hit enterthis should clear the debuug log.
We are nonetheless closer to identifying the problem, because the sync no longer runs in parallel, so it's much easier to read the debug output -- if you would do the honors of providing the logs one more time :)
@tkurbad commented on GitHub (Nov 25, 2018):
Hmm, clearing the log didn't prevent the quota message from reappearing.
New debug.log: https://gist.github.com/tkurbad/2fc61f0fbcdcc461657127aa73c2b07d
@marcelklehr commented on GitHub (Nov 25, 2018):
Thanks so much. I was able to isolate, reproduce and fix the bug. Just released a new version.
@tkurbad commented on GitHub (Nov 25, 2018):
Sorry @marcelklehr, but I'm still getting the "Index out of bounds" error. Debug log again? ;-)
@tkurbad commented on GitHub (Nov 25, 2018):
New debug.log: https://gist.github.com/tkurbad/554cc5edf927ccfb6d35bb2a64627501
@marcelklehr commented on GitHub (Nov 25, 2018):
Wow, your bookmarks are a goldmine for finding bugs! :)
This one is the same error but a different cause. Should be fixed now, as well.
@tkurbad commented on GitHub (Nov 26, 2018):
And once again: https://gist.github.com/tkurbad/aad2e4b6be6bebbd01b31388b1c750dc
This time, however, I got a folder and contents locally that previously only existed on the NC server. So, we are making visible progress! ;-)
@marcelklehr commented on GitHub (Nov 26, 2018):
This is amazing 🙀 I've never fixed so many bugs from one report before :D
@marcelklehr commented on GitHub (Nov 26, 2018):
Bugfix release is out. :)
@tkurbad commented on GitHub (Nov 26, 2018):
Keep'em bugfixes comin'! ;-)
New debug.log (still "Index out of bounds"): https://gist.github.com/tkurbad/bbf67a4a89a701a7ccd87455b3737456
@marcelklehr commented on GitHub (Nov 26, 2018):
mmh. I think this log was cut off. Possibly by chrome's quota. Can you clear the logs again and capture a new log?
@tkurbad commented on GitHub (Nov 26, 2018):
Actually, it seems to be a problem with gist. Log is now in this OC-share: https://owncloud.iwm-tuebingen.de/s/n8povKTwgGLqYTy
@marcelklehr commented on GitHub (Nov 26, 2018):
Fix is out... ;D
@tkurbad commented on GitHub (Nov 26, 2018):
Thanks! I'm afk at the moment. Will check tomorrow morning.
@tkurbad commented on GitHub (Nov 27, 2018):
Next round! :-)
debug.log again in the owncloud share.
@tkurbad commented on GitHub (Nov 29, 2018):
@marcelklehr Are you still with me? ;-)
@marcelklehr commented on GitHub (Nov 29, 2018):
Yes! I'm with you. I've been tending to other issues as well, though, so I haven't published another bugfix release yet, but this is your fix:
github.com/marcelklehr/floccus@f2ec29edb6:D@marcelklehr commented on GitHub (Nov 30, 2018):
v3.1.14 has been released, your turn @tkurbad :D
@tkurbad commented on GitHub (Nov 30, 2018):
Cool! "Successfully ended sync process for account ..."
Thanks so much for your time and efforts. I'll try and merge with the bookmarks of my other computer on Monday and report back.
This can be closed for now, I suppose...
@marcelklehr commented on GitHub (Nov 30, 2018):
ooph. 🎉
You're welcome :D
@onny commented on GitHub (Dec 22, 2018):
Hey @marcelklehr thank you for this nice extension! I'm getting the same error in
brave 0.57.18andnextcloud 15.0.0withbookmarks app 0.14.3, see the log here:https://onny.project-insanity.org/files/floccus-3.2.0-2018-12-22%20(1).log
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.