Hi, all There is another server which has the anchors mismatch problem except ZYB. So is it possible to avoid anchor checking in a sync client? I don't know whether it could lead to other issues but this could help prevent the problem stated here.
Cheers, Yongsheng From: Zhu, Yongsheng Sent: Thursday, November 12, 2009 5:23 PM To: 'Björn Isaksson' Cc: Ohly, Patrick; '[email protected]' Subject: RE: An issue of interoperability test with Mobical The current behavior of client checks the anchors because under this circumstance we think there was an error and client should initiate a slow sync to avoid errors. Anyway, thanks for your clarification. Cheers, Yongsheng From: Björn Isaksson [mailto:[email protected]] Sent: Thursday, November 12, 2009 4:53 PM To: Zhu, Yongsheng Subject: Re: An issue of interoperability test with Mobical Hi, you're right. The server does not correctly save the anchor in a one-way-from-client sync. Why do you check the server's anchors? As a client you only have the option to ignore any error or to abort the session. /Björn Zhu, Yongsheng wrote: Hi, Björn Our nightly test found an issue when testing 'one-way-from-client' sync mode. Our test case has many steps: get both clients and server in sync with no items anywhere http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.deleteall.init.client.A/ http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.deleteall.twoway.client.A/ http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.deleteall.init.client.B/ http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.deleteall.twoway.client.B/ add one item on first client A, copy to server http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.send.client.A/ add a different item on second client B, one-way-from-client http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.send.client.B/ two-way sync with first client A => two items on first client, one on second http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.check.client.A/ delete on second client B, sync that to first client A via one-way-from-client, two-way http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.delete.client.B/ one item left on first client (the one inserted locally) The error occurs in step 5. Server sends a different 'last' anchor mismatched with the last sync. Thus, a slow sync is triggered. But it should not have any errors between two syncs. We don't know why server sends this. See below detailed html and search 'Saved Last Remote Server Anchor'. http://runtests.syncevolution.org/2009-11-10-22-00/head-evolution-testing/12-mobical/Client_Sync_ical20_testOneWayFromClient.delete.client.B/sysynclib_linux.html Björn, could you have a check? Regards, Yongsheng _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
