Bug 52686 - automatic error recovery
Summary: automatic error recovery
Status: RESOLVED MOVED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: SyncEvolution (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 11:52 UTC by Patrick Ohly
Modified: 2018-10-13 12:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Patrick Ohly 2012-07-29 18:36:00 UTC


---- Reported by patrick.ohly@intel.com 2011-10-26 11:52:12 +0000 ----

At the moment there are situations where SyncEvolution cannot determine what the right resolution for a failed synchronization is. It has a built-in backup mechanism and can ask the user for assistance, but ultimately it would be better to not bother the user. This can be achieved in some cases by simplifying the problem:

 * The peer (most likely a service on the Internet) must be able to store all data.
 * There is a separate local database for each database on the peer.

In that case it is acceptable to wipe out the local data and restart with the data stored on the peer:

* Implement the necessary policy in SyncEvolution ("peer wins").
* Check whether this interferes with libfolks (local IDs will change, data added by libfolks to a contact might get lost).



--- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC  ---

This bug was previously known as _bug_ 23765 at https://bugs.meego.com/show_bug.cgi?id=23765
Comment 1 GitLab Migration User 2018-10-13 12:41:12 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/59.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.