http://bugzilla.moblin.org/show_bug.cgi?id=9776 Summary: expiring session dirs: error handling Classification: Moblin Projects Product: SyncEvolution Version: upstream Platform: Netbook OS/Version: Moblin Linux Status: ASSIGNED Severity: normal Priority: P2 Component: *Feature Request AssignedTo: patrick.ohly(a)intel.com ReportedBy: patrick.ohly(a)intel.com CC: syncevolution(a)lists.intel.com Right now, any kind of exception thrown inside LogDir::expire() will abort the function. It gets caught in the general exception handling code and is reported. The problem is that the exception might be thrown each time we attempt to remove old sessions, thus preventing any kind of automated removal of them. The error reporting doesn't mention that. One way to trigger such a situation is this: - sync twice, without making changes - in the first session, remove a ".after" dump - continue syncing This should lead to haveDifferentContent() failing to read the content of the first session and an error message like: Data modified locally during synchronization: *** vcard30 *** no changes [ERROR] /home/pohly/.cache/syncevolution/scheduleworld__1(a)client_+test_+1-2010-02-08-10-28/ical20.after: No such file or directory We should introduce some kind of exception handling in expire() and cope with failures more gracefully. The exact kind of handling needs to be determined. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.