-
Notifications
You must be signed in to change notification settings - Fork 670
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
setSelectiveSyncList is not transactional: selective sync entries lost in sqlite.db #6431
Comments
BTW: I won't be able to follow up on this for several days. |
Right, SyncJournalDb::setSelectiveSyncList should be made more transactional. |
@ogoffart setDataFingerprint too? Or change it to use INSERT OR REPLACE? |
@guruz setDataFingerprint is already in a transaction because it is called from the sync engine in which everything is in a transaction. |
Question: can the loss of selective sync information also happen due to client shutdown while auto-update? We have such cases reported. |
Not that i am aware of. |
But the fix above was only done in 2.5.0, so upgrades to 2.4.x may still be affected by the original bug. |
It depends if the auto-update closes the sync client "gracefully" or not. I
don't know how sparkle and msi do it.
…On Tue, Oct 9, 2018 at 5:25 PM Olivier Goffart ***@***.***> wrote:
But the fix above was only done in 2.5.0, so upgrades to 2.4.x may still
be affected by the original bug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6431 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAl9jbO-J8zztvZffojkhuKaOdFPBn8Fks5ujL_lgaJpZM4TJkOg>
.
--
---
Best regards,
Kuba
|
MacOSX, client 2.3.3 (and versions before)
This happens quite often when I have a disk full or on system shutdown.
Selective sync information is lost. It looks like this is not committed as a proper transaction. When this happens sync client complains about big folders and asks for action.
As a result I have to redefine and exclude from sync big folders manually every time (in the selective sync tree). This is very annoying and error prone.
Normally it looks like this:
When the problem occurs it looks like this:
@SamuAlfageme : you have seen this problem live at last workshop ;-)
The text was updated successfully, but these errors were encountered: