Ticket #529 (closed defect: worksforme)

Opened 4 years ago

Last modified 4 years ago

bug: file-sync <--> file-sync

Reported by: dfriedrich Owned by: dfriedrich
Priority: highest Milestone: OpenSync 0.40
Component: OpenSync Version: 0.32
Severity: blocker Keywords:
Cc:

Description

In both folders of the file-sync plugin is a file with the same name but differnt content.

sync --> works sync again --> do not work sync again --> works (because slow sync) sync again --> do not work sync again --> works ...

Problem: Mybe the mapping wont be created?

Attachments

trace-files-uid-problem.tar Download (180.0 KB) - added by cstender 4 years ago.

Change History

comment:1 Changed 4 years ago by cstender

  • Milestone changed from 0.31 to OpenSync 0.40

Milestone 0.31 deleted

comment:2 Changed 4 years ago by cstender

I can reproduce this with irmc-sync to file-sync.

1.) added contact to the phone 2.) initial sync (slow-sync works fine) 3.) second sync (fast-sync works fine) 4.) added another contact to the phone 5.) third sync (fast-sync)

Now I get this error: [...] All clients sent changes or error All conflicts have been reported opensync/data/opensync_change.c:189:E:osync_change_set_uid: Assertion "uid" failed Abgebrochen

Changed 4 years ago by cstender

comment:3 Changed 4 years ago by cstender

  • Priority changed from normal to highest
  • Version changed from 0.31 to 0.32
  • Severity changed from normal to blocker

comment:4 Changed 4 years ago by cstender

Okay, this has nothing to do with my irmc problem. Nevertheless I can't reproduce your file sync problem.

comment:6 Changed 4 years ago by dgollub

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

I can't reproduce this - could you give more detailed steps how to reproduce this? Or check if you still able to reproduce this:

The sync was successful
dani@K51:~/Sync/file> echo "XXX" > 1/data/ooo
dani@K51:~/Sync/file> echo "YYY" > 2/data/ooo
dani@K51:~/Sync/file> rm /tmp/osync_trace/*; msynctool --sync file2file
Synchronizing group "file2file" 
data sink of member 2 of type file-sync just connected
Main sink of member 2 of type file-sync just connected
data sink of member 1 of type file-sync just connected
Main sink of member 1 of type file-sync just connected
All clients connected or error
Received a entry ooo from member 1 (file-sync). Changetype ADDED
data sink of member 1 of type file-sync just sent all changes
Main sink of member 1 of type file-sync just sent all changes
Received a entry ooo from member 2 (file-sync). Changetype ADDED
data sink of member 2 of type file-sync just sent all changes
Conflict for Mapping 0x8097ed0: 
Entry 1:
Member: 1 (file-sync)
UID: ooo
File ooo: size: 4

Entry 2:
Member: 2 (file-sync)
UID: ooo
File ooo: size: 4

Which entry do you want to use? [1-9] To select a side, [D]uplicate: d
Mapping duplicated
Main sink of member 2 of type file-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Main sink of member 1 of type file-sync committed all changes.
data sink of member 1 of type file-sync committed all changes.
Main sink of member 2 of type file-sync committed all changes.
Sent a entry ooo to member 2 (file-sync). Changetype MODIFIED
Sent a entry ooo-dupe to member 2 (file-sync). Changetype ADDED
data sink of member 2 of type file-sync committed all changes.
All clients have written
data sink of member 1 of type file-sync reported sync done.
data sink of member 2 of type file-sync reported sync done.
Main sink of member 2 of type file-sync reported sync done.
Main sink of member 1 of type file-sync reported sync done.
All clients reported sync done
data sink of member 1 of type file-sync just disconnected
Main sink of member 1 of type file-sync just disconnected
data sink of member 2 of type file-sync just disconnected
Main sink of member 2 of type file-sync just disconnected
All clients have disconnected
The sync was successful

Nice .. i hit bug in duplicate conflict handler looks like it's again broken. Anway - please reopen the if you still can reproduce.

Note: See TracTickets for help on using tickets.