Ticket #636 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

slow-sync causes all calendar entries to be duplicated on my Nokia E65

Reported by: stuart Owned by: dgollub
Priority: normal Milestone:
Component: OpenSync Version: 0.22
Severity: major Keywords:
Cc:

Description

I had a sync that failed and so the next sync was a slow sync. This caused all the calendar entries to be duplicated. Instead of 800 entries I had 1600 which was a real pain to deal with.

I did a small test to check that this is a real bug. I removed all the calendar entries from my telephone and, using new sync profiles on the telephone and in OpenSync, I synced them back to the telephone. I then forced a slow-sync and indeed found all the entries in the phone twice.

This is a real problem because it means that if I have a sync that fails for any reason, the next sync will duplicate all my entries and stuff up my diary!

% msynctool --delgroup NokiaE65Calendar_file
% msynctool --addgroup NokiaE65Calendar_file
% msynctool --addmember NokiaE65Calendar_file file-sync
% msynctool --addmember NokiaE65Calendar_file syncml-obex-client
% msynctool --configure NokiaE65Calendar_file 1
% msynctool --configure NokiaE65Calendar_file 2
% msynctool --sync NokiaE65Calendar_file  > sync.out
% tail -3 sync.out 
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful
% msynctool --sync NokiaE65Calendar_file --slow-sync event > resync.out
% tail -3 resync.out
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync was successful

Attachments

sync.out (9.1 KB) - added by stuart 6 years ago.
the output of the first (normal) sync
resync.out (9.1 KB) - added by stuart 6 years ago.
the output of the sync that caused all entries to be duplicated

Change History

Changed 6 years ago by stuart

the output of the first (normal) sync

Changed 6 years ago by stuart

the output of the sync that caused all entries to be duplicated

comment:1 Changed 6 years ago by dgollub

  • Status changed from new to closed
  • Resolution set to fixed

This is known issue of not proper handling of different capabilities of different sync parties. With 0.3x development we introduced capabilities handlers which demerge/merge capabilities/fields which are known not to be supported by the party.

The duplication happens when two logical same entries get compared and doesn't result as similar/same entry. The reason for this is that unsupported field "silently" got thrown away by the member which didn't support this capability.

Please have another try with stable release of OpenSync 0.40 (Fixed with 0.40 - not yet released.)

Note: See TracTickets for help on using tickets.