-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
Bookmarks can't be synchronized and show "Scheduled" #1548
Comments
Hello 👋 Thank you for taking the time to open this issue with floccus. I know it's frustrating when software I look forward to working with you on this issue |
try to delete the .lock file |
After deleting the. lock file, it will appear soon. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Please make sure
Judging from the chrome webstore statistics there are still around 800 Chrome instances on v5.0.6, which has this bug. |
I've updated all device versions to 5.0.9, two EDGE, and one mobile browser, and I'm still having this problem. |
see #1548 Signed-off-by: Marcel Klehr <mklehr@gmx.net>
So, this should only really be a problem when syncing via WebDAV like @Ganya-A and @idzyr and @beyercj @InfamousUser is syncing via Nextcloud Bookmarks, which should automatically timeout its lock. Is this still happening for you? @traviss64 are you syncing via Nextcloud Bookmarks or via Nextcloud files (ie. webdav)? |
@marcelklehr |
This should be resolved with v5.0.10, please let me know if it works :) |
Updated to v5.0.10 on Chrome, no change. |
Updated to v5.0.10 on Firefox 115.8.0esr for Linux and to v5.0.11 on Android 11 on Samsung Galaxy A12, no change either on webdav.smartdrive.web.de (webspace almost full). However, synchronisation worked fine on webdav.vodafonemail.de (webspace almost empty), so might not have anything to do with floccus. |
So, this issue usually stems from a leftover lock file that prevents all clients from syncing. v5.0.10 should mitigate that by forcing floccus to sync anyway, if it has waited long enough. If this does not fix this for you all, then we might have a more serious issue of an interrupted sync process. This would be the case if for example if floccus does sometimes start to sync but then stops, likely after about 5mins, only to then show the "scheduled Sync" message one minute later, which again stems from the leftover lock file. On firefox I think you can also verify if this is the problem by opening the browser debug log. The browser will then no longer interrupt the sync process and thus floccus should sync correctly after some time waiting for the lock to expire and go back to an "All good" green status, while the debug window is open. Here's how to open the debug window: Firefox
Not sure, if this will work in chrome, but you may try: Chrome
|
I am receiving "QUEUING POST", "FETCHING POST", "Receiving response for POST" and then "Resource is locked, trying again soon" in the Floccus logs. I should note that it did sync the folders to the server, but none of the actual bookmarks are populated. |
@InfamousUser You will need to wait until the lock is cleared for the above thing with the debug window to work. Only unpopulated folders is a bad sign, though... |
How long do I need to wait? Sever has been off for the past few days, I just turned it on and still the same problem. Is there a way to force this or what am I supposed to do? |
Doesn't matter anymore, I've been able to reproduce this now and can debug from there. It looks like Chrome blatantly shuts down extension service workers after running some amount of minutes. There's not gonna be an easy fix for this, I think. Should still be doable though |
I also have this problem. Two Firefox browsers using v5.0.10 (though one was recently on 5.0.5). My server does have a lock file on it. |
Add a new account and use other ways of sync for now.Hope the author solve the problem soon. |
Updated Firefox from 5.0.8 to 5.0.10 and within a short time the lock file imposed itself. Is rollback possible? I deleted the lock file, but can't do that regularly. I'm using WebDAV. |
I delete the lock file ,then remove my account and re-add it. You can try this too, no loss anyway |
No need to remove account. Disable all Floccus extensions. Delete lock file. Enable all Floccus extensions. Not something one wants to do multiple times a day. |
@cng10001 You will still need to wait or remove the lock manually, initially, as described above. Afterwards it shouldn't get stuck like this anymore. |
Any other testers? Would be great if a few of you could test this, otherwise I have to release it untested :S |
Well, unlike the previous version, this one did manage to sync something. It synced around 150 bookmarks before going to the "Scheduled" stage and stopping there. Errors in the log are identical to the post #1548 (comment) or being E017 network error which changes to the "This profile will be synced soon..." one upon depressing the sync now button. It is periodically switching between syncing and scheduled with syncing only for a few seconds but no additional bookmarks being synced. |
@InfamousUser Thank you for taking it for a spin! Are there any other floccus instances running that haven't been updated to the beta version, yet? |
There is the original Floccus, the beta doesnt update it but make an additional extension unfortunately. It had its autosync disabled though and hasn't synced as far as I'm aware and the last error in its log is 17.03.2024. I can delete it if you think it's interfering in some way? |
Mh, probably best to disable the original extension instance, yeah |
I disabled the real extension in settings. It seems to be randomly syncing more bookmarks but this is not what I would call a working fix. It has synced another 100 or so bookmarks. When you press the sync it latches but then it keeps switching between syncing and scheduled. Bu then after a while it "finishes" and you have to trigger it again because it has not synced the bookmarks. |
Maybe my problem is I was still using a lower version of chrome, |
@InfamousUser Can you confirm whether it syncs for roughly 5 minutes, at least, before it switches back to "scheduled"? |
Chrome version may be interesting as well, indeed. Chrome v110+ may be necessary for some of this to work properly |
I do not and cannot have Chrome v110+ due to Google blocking updates on older Windows so count me out for testing that... |
Oh Wow! So you do have pre v110 Chrome, so the fix I built may work after all. Sorry about the Chrome updates! |
Geez, never thought that'd be the issue! I can try it on a different PC, with newer browser, but I have a feeling that will work since it doesn't really help! Will get back to you with the results! |
It's not the root cause, but part of my fix only works post v110 |
Alright, since it works for me I'll roll this out stage-wise in production now to get people to test it. |
Just to confirm the fix works for me, but everyone already knows I guess. |
Thank you @InfamousUser always good to get confirmation :) |
where is the .lock file on nextcloud? |
@ivanjx please open a new discussion or a new issue |
Which version of floccus are you using?
5.0.8 5.0.9
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Edge
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
jianguoyun
Describe the Bug
I can't get both of my computers to sync.
Scheduled:This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing.
Expected Behavior
To Reproduce
Debug log provided
The text was updated successfully, but these errors were encountered: