Hello Patrick,
On Nov 10, 2009, at 19:31 , Patrick Ohly wrote:
> On Tue, 2009-11-03 at 18:23 +, Lukas Zeller wrote:
>> On Nov 3, 2009, at 14:09 , Patrick Ohly wrote:
>>> Second observation: the failure is not recorded and thus doesn't
>>> show up
>>> in the sync statistics or the overall sy
On Tue, 2009-11-03 at 18:23 +, Lukas Zeller wrote:
> Hello Patrick,
>
> On Nov 3, 2009, at 14:09 , Patrick Ohly wrote:
> > Second observation: the failure is not recorded and thus doesn't
> > show up
> > in the sync statistics or the overall sync result. Is this expected?
>
> Not really. I'
Hello Patrick,
On Nov 3, 2009, at 14:09 , Patrick Ohly wrote:
I have checked, the InsertItemAsKey() implementation returns a 510
error
code. This error code is passed up until it reaches
sysync::TBinfileImplDS::implProcessItem(), where it is handled like
this:
1962error:
1963 // report
Hello!
A SyncEvolution user reported that despite an error printed by
SyncEvolution's calendar backend, overall the sync was said to be
successful:
http://bugzilla.moblin.org/show_bug.cgi?id=7755
I have checked, the InsertItemAsKey() implementation returns a 510 error
code. This error code is pas
