http://bugzilla.meego.com/show_bug.cgi?id=1019 Summary: expiring session dirs: error handling Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: Netbook OS/Version: IA Status: ASSIGNED Severity: enhancement Priority: Medium Component: GTK UI AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: jingke.zhang(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-gtk-ui-bugs(a)meego.bugs Estimated Hours: 0.0 This is from http://bugzilla.moblin.org/show_bug.cgi?id=9776 Description From pohly 2010-02-19 08:51:47 PST (-) [reply] 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.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.