[GH-ISSUE #848] why Synchronization strategy changes itself for Chromium #546

Closed
opened 2026-02-25 22:37:27 +03:00 by kerem · 14 comments
Owner

Originally created by @candrapersada on GitHub (Mar 7, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/848

Describe the bug

why Synchronization strategy changes itself from Always revert upstream remote changes and push local changes to Merge local and remote changes (recommended) when I sync manually

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'floccus'
  2. Click on 'Sync up'

Expected behavior

Synchronization strategy tabs settings change when manually syncing

Desktop

  • OS: Windows 10 Home
  • Browser Firefox and Chromium
  • Floccus version: 4.6.1
  • Floccus sync method: Google Drive
Originally created by @candrapersada on GitHub (Mar 7, 2021). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/848 ### Describe the bug why Synchronization strategy changes itself from Always revert upstream remote changes and push local changes to Merge local and remote changes (recommended) when I sync manually ### To Reproduce Steps to reproduce the behavior: 1. Go to 'floccus' 2. Click on 'Sync up' ### Expected behavior Synchronization strategy tabs settings change when manually syncing ### Desktop - OS: Windows 10 Home - Browser Firefox and Chromium - Floccus version: 4.6.1 - Floccus sync method: Google Drive
kerem 2026-02-25 22:37:27 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@marcelklehr commented on GitHub (Mar 7, 2021):

Confirmed.

<!-- gh-comment-id:792257272 --> @marcelklehr commented on GitHub (Mar 7, 2021): Confirmed.
Author
Owner

@marcelklehr commented on GitHub (Mar 7, 2021):

Fixed. Will be released soon. Thanks for reporting 😊

<!-- gh-comment-id:792257425 --> @marcelklehr commented on GitHub (Mar 7, 2021): Fixed. Will be released soon. Thanks for reporting :blush:
Author
Owner

@candrapersada commented on GitHub (Mar 13, 2021):

The time between two synchronizations runs in a few minutes. The default is 15 minutes. when the browser starts sync runs itself before 15 minutes
for example when I start the browser after 1 day close the sync starts immediately before 15 minutes why this happens?
image

<!-- gh-comment-id:798802783 --> @candrapersada commented on GitHub (Mar 13, 2021): The time between two synchronizations runs in a few minutes. The default is 15 minutes. when the browser starts sync runs itself before 15 minutes for example when I start the browser after 1 day close the sync starts immediately before 15 minutes why this happens? ![image](https://user-images.githubusercontent.com/36833664/111053043-21f9a580-8493-11eb-990b-c10c4021c0ea.png)
Author
Owner

@marcelklehr commented on GitHub (Mar 17, 2021):

for example when I start the browser after 1 day close the sync starts immediately before 15 minutes why this happens?

This is because floccus calculates the time between sync runs. If the last sync run was more than 15min ago, it will run a sync, even if the browser was just started.

<!-- gh-comment-id:801105149 --> @marcelklehr commented on GitHub (Mar 17, 2021): > for example when I start the browser after 1 day close the sync starts immediately before 15 minutes why this happens? This is because floccus calculates the time between sync runs. If the last sync run was more than 15min ago, it will run a sync, even if the browser was just started.
Author
Owner

@marcelklehr commented on GitHub (Mar 17, 2021):

I cannot reproduce this issue anymore with v4.6.1. Can you make sure you are running this latest version?

<!-- gh-comment-id:801105505 --> @marcelklehr commented on GitHub (Mar 17, 2021): I cannot reproduce this issue anymore with v4.6.1. Can you make sure you are running this latest version?
Author
Owner

@candrapersada commented on GitHub (Mar 17, 2021):

I cannot reproduce this issue anymore with v4.6.1. Can you make sure you are running this latest version?

yes this is the latest version.

  • Browser Chromium
<!-- gh-comment-id:801282999 --> @candrapersada commented on GitHub (Mar 17, 2021): > I cannot reproduce this issue anymore with v4.6.1. Can you make sure you are running this latest version? yes this is the latest version. - Browser Chromium
Author
Owner

@candrapersada commented on GitHub (Mar 19, 2021):

the problem is in chromium.

<!-- gh-comment-id:802588373 --> @candrapersada commented on GitHub (Mar 19, 2021): the problem is in chromium.
Author
Owner

@marcelklehr commented on GitHub (Mar 19, 2021):

I cannot reproduce this in Chromium either.

This is what I tried:

  1. Create Google Drive sync Account
  2. set push sync strategy
  3. click push sync / pull sync / normal sync in overview panel
  4. refresh account settings
  5. sync strategy is still push sync

What did you do?

<!-- gh-comment-id:802797973 --> @marcelklehr commented on GitHub (Mar 19, 2021): I cannot reproduce this in Chromium either. This is what I tried: 1. Create Google Drive sync Account 2. set push sync strategy 3. click push sync / pull sync / normal sync in overview panel 4. refresh account settings 5. sync strategy is still push sync What did you do?
Author
Owner

@candrapersada commented on GitHub (Mar 19, 2021):

but the sync strategy still changes itself for tabs chromium. from push sync changes to pull sync when pull sync manually.
after importing configurations from floccus v4.6.0 to v4.6.1

<!-- gh-comment-id:803037532 --> @candrapersada commented on GitHub (Mar 19, 2021): but the sync strategy still changes itself for tabs chromium. from push sync changes to pull sync when pull sync manually. after importing configurations from floccus v4.6.0 to v4.6.1
Author
Owner

@marcelklehr commented on GitHub (Mar 19, 2021):

Aha. For tabs. I'll try that.

<!-- gh-comment-id:803051028 --> @marcelklehr commented on GitHub (Mar 19, 2021): Aha. For tabs. I'll try that.
Author
Owner

@candrapersada commented on GitHub (Mar 19, 2021):

after updating or importing configurations from floccus v4.6.0 to v4.6.1

<!-- gh-comment-id:803051602 --> @candrapersada commented on GitHub (Mar 19, 2021): after updating or importing configurations from floccus v4.6.0 to v4.6.1
Author
Owner

@marcelklehr commented on GitHub (Mar 20, 2021):

This only happens when opening settings while the pull sync is running. When sync strategy is set to push, and you manually pull, the strategy is temporarily changed to pull, until after the sync run, when it is reset to push. This is by design.

<!-- gh-comment-id:803299472 --> @marcelklehr commented on GitHub (Mar 20, 2021): This only happens when opening settings while the pull sync is running. When sync strategy is set to push, and you manually pull, the strategy is temporarily changed to pull, until after the sync run, when it is reset to push. This is by design.
Author
Owner

@candrapersada commented on GitHub (Mar 20, 2021):

but why only happens for chromium tabs?

<!-- gh-comment-id:803445982 --> @candrapersada commented on GitHub (Mar 20, 2021): but why only happens for chromium tabs?
Author
Owner

@github-actions[bot] commented on GitHub (Mar 20, 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.

<!-- gh-comment-id:1476937717 --> @github-actions[bot] commented on GitHub (Mar 20, 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#546
No description provided.