http://bugzilla.moblin.org/show_bug.cgi?id=9156
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2010-01-21 02:57:33 PST ---
(In reply to comment #2)
(In reply to comment #1)
> This is the first time to do sync, and if doing two-way, syncevolution has to
> initiate a slow-sync. so it's failed. But I think this is not friendly to users
> as we may not know much about the sync mode. Also the detailed description
> should be shown in the screen.
Not showing an explanation is the real problem here.
The reason was that the code which aborted the sync and prints the explanation
wasn't triggered here: the Synthesis engine stops all by itself because the
only active source failed.
I changed the printing of the explanation so that:
- it is printed when aborting, to explain the ERROR
that is printed there
- it is always (including the previous case) printed
again underneath the final status overview produced
by the command line
For this to work without code duplication, the formatting of the explanation
was moved into SyncReport. It kind of fits there because the message can be
generated for a SyncReport instance. For that case it would be nice if the
actual peer name used for that sync session was in the report; I didn't want to
make too many changes at once, though.
The output looks like this:
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| vcard30 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 34 before sync, 34 after it |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Thu Jan 21 11:51:38 2010, duration 0:01min |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: unexpected slow sync (local, status 22000)
Doing a slow synchronization may lead to duplicated items or
lost data when the server merges items incorrectly. Choosing
a different synchronization mode may be the better alternative.
Restart synchronization of affected source(s) with one of the
following sync modes to recover from this problem:
slow, refresh-from-server, refresh-from-client
Analyzing the current state:
syncevolution --status scheduleworld_1 vcard30
Running with one of the three modes:
syncevolution --sync [slow|refresh-from-server|refresh-from-client]
scheduleworld_1 vcard30
Jussi, can you review mb9156 so that I can merge today?
--
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.