http://bugzilla.moblin.org/show_bug.cgi?id=2416
--- Comment #6 from pohly <[email protected]> 2009-12-15 09:07:00 PST --- I was hoping that I could let "good" sources continue in a sync while disabling "bad" ones which ran into an unexpected slow sync. I couldn't quite get this to work with ABORTDATASTORE() in an <alertscript>, the client and server didn't properly continue with the session (Alert 222 loop). What seems to work, at least on the client side at the moment, is to flag the bad datastores and then abort the whole session. Progress events are a bit weird, but the final status is okay: [INFO] addressbook: starting normal sync, two-way [INFO] calendar: inactive [ERROR] calendar: failed with status code 10000 [INFO] addressbook: normal sync done unsuccessfully [ERROR] addressbook: failed with status code 10001 [INFO] calendar: starting slow sync, two-way Synchronization failed, see /home/pohly/.cache/syncevolution/syncevolution__client-2009-12-15-17-53/syncevolution-log.html for details. Changes applied during synchronization: +---------------|-------ON CLIENT-------|-------ON SERVER-------|-CON-+ | | rejected / total | rejected / total | FLI | | Source | NEW | MOD | DEL | NEW | MOD | DEL | CTS | +---------------+-------+-------+-------+-------+-------+-------+-----+ | addressbook | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 | | two-way, 0 KB sent by client, 0 KB received | | item(s) in database backup: 34 before sync, 34 after it | | synchronization failed (status code 10001) | +---------------+-------+-------+-------+-------+-------+-------+-----+ | calendar | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 | | slow, 0 KB sent by client, 0 KB received | | item(s) in database backup: 13 before sync, 13 after it | | synchronization failed (status code 10000) | +---------------+-------+-------+-------+-------+-------+-------+-----+ | start Tue Dec 15 17:53:10 2009, duration 0:02min | | synchronization failed (status code 10001) | +---------------+-------+-------+-------+-------+-------+-------+-----+ Status 10000 == unexpected slow sync. Status 10001 == aborted session because some other source ran into unexpected slow sync, can be ignored. Status codes are tentative at this point. I can do a two-way sync with "addressbook" and once a slow sync is forced for "calendar", also sync that again. Is this a useful mode of operation? There's one unsolved problem with it: when both "addressbook" and "calendar" would have unexpected slow syncs, only one sync mode is checked before aborting the whole session. The result is the same as above, whereas the correct result would be status 10000 for *both* sources. Need to check whether I can place the ABORTSESSION() elsewhere. -- 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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
