mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #709] Updated to 4.4.2 and nothing is working on multiple clients #453
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#453
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 @dsiminiuk on GitHub (Oct 27, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/709
Describe the bug
Sync doesn't work at all. Progress bar sits at 5% (?) and never moves, never times out (or I'm not patient enough) :)
Clicking the "Debug Logs" button does not render a log file.
To Reproduce
Setup/import account, click sync or upgrade to 4.4.2.
Makes no difference what settings you use, merge local, merge remote, trigger from scratch (dangerous).
Firewall is disabled.
Expected behavior
Sync would happen
Desktop (please complete the following information):
Server (please complete the following information):
Debug log
CAN'T PRODUCE IT! see above.
@marcelklehr commented on GitHub (Oct 27, 2020):
Are you sure you're using "nextcloud legacy"? Your screenshot reads "nextcloud-folders". The legacy sync method was deprecated starting in v4.0 and has been removed in v4.4.x.
If the debug log is not available you can debug via browser tools as follows:
Firefox
about:debuggingdebugbutton next to floccus entrysync nowfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the account of your choice@marcelklehr commented on GitHub (Oct 27, 2020):
It just occurred to me that you may likely experience an uncleared lock. To clear it, you can go to your nextcloud files, enable the display of hidden files and delete all files named
.floccus-xxxxx.lock.@dsiminiuk commented on GitHub (Oct 27, 2020):
I'm using Nextcloud Bookmarks, sorry.
chrom://extensions redirects to vivaldi://extensions/
Already in developer mode, that's how I uploaded the crx file.
Regarding your lock file idea, that could be the case. It would explain why nothing is moving on all my browsers. Now to figure out how to display hidden files...
@marcelklehr commented on GitHub (Oct 27, 2020):
It's in the settings of the files app, bottom-left corner. ;)
@dsiminiuk commented on GitHub (Oct 27, 2020):
Yup there it is and there is the .lock file. Thank you. Let me test and see if I can get my sanity back.
@marcelklehr commented on GitHub (Oct 27, 2020):
Perhaps an automatic process for removing the lockfile after a certain amount of stale time is in order.
@dsiminiuk commented on GitHub (Oct 27, 2020):
By the way, by the time I went to clear the lock file there was an error on the sync dialog that said the same thing, "consder clearing (it)". Perhaps on the next iteration you can change the timeout or check the age of the lock file and show the error a little sooner than what felt like forever.
Progress, sync started working again but I have an error...
I'll try a trigger from scratch to clear the server list.
@dsiminiuk commented on GitHub (Oct 27, 2020):
Deleted bookmarks on the server, forced upload from the client.
Got this the first time
Set the client to merge then got this error.
@dsiminiuk commented on GitHub (Oct 27, 2020):
then
@dsiminiuk commented on GitHub (Oct 27, 2020):
Tried closing the browser, then clicking the Upload button.
@marcelklehr commented on GitHub (Oct 27, 2020):
oof. I can confirm that some things are boken in v4.4.x so far, which is why I've held off publishing it on the chrome webstore so far. I'll be doing a new release today or tomorrow, though, let's see how that fares.
@dsiminiuk commented on GitHub (Oct 27, 2020):
OK I got it fixed up on one client. I cleared the bookmarks on the server, deleted the bookmarks on the browser (some folders were corrupted because I tried Vivaldi Sync and that created a mess).
I imported a backup of my bookmarks (clean) back into the browser and then the upload went fine.
On to other browsers...
@dsiminiuk commented on GitHub (Oct 27, 2020):
Cleared bookmarks on a second machine and clicked the Down Arrow to import. No problem.
I think I'm good now.
@marcelklehr commented on GitHub (Oct 27, 2020):
Backups ftw! 🚀
@dsiminiuk commented on GitHub (Oct 27, 2020):
Another enhancement (yes) would be to clearly label the Enable switch as "Auto sync" and still allow the Up and Down arrows to do manual forced sync without Auto being enabled. A user might want to download and not auto-update until all clients are synced and safe. Just an idea.
As it is now I think the account needs to be enabled before Up and Down forced will work. Correct?
@marcelklehr commented on GitHub (Oct 27, 2020):
Mh, no. The Up/Down buttons temporarily enable the account.
@dsiminiuk commented on GitHub (Oct 27, 2020):
OK great.
@marcelklehr commented on GitHub (Oct 27, 2020):
I'm open to any other enhancements / UX improvements you may have, though :) Feel free to open issues! ❤️
@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.