Home > Event, ownCloud > ownCloud Client May Hackfest

ownCloud Client May Hackfest

Again we’re meeting in Berlin at Woboq Intl. Headquarters to work on the ownCloud Sync Client again. One of our topics is the still not completely fixed problem with conflict files. There has been lots of troubles about false conflict files the client is generating in that situations were the ETag database is wasted.

We revisited this problem and will come up with a better solution.

The key changes will probably be

  • Conflict files will never again be generated on the server. Even if we are in a conflict situation, we will download the file and keep the conflicting version only on the client. This enables us to detect false conflicts.
  • The current way we handle a system time difference has to be changed. We wont adjust the file mtimes of files in the file system any more with the time difference between the client and server. That way we do not suffer from floating time differences any more.
    For the decision of which version is more recent, we will still consider the time difference.
  • We will use a very quick request like OPTION to get the servers time setting to the client. That will allow to calculate the time difference between server and client more accurately. It’s needed to decide which file is more recent.

Read this as a note to self, yet we feel very well fitting into Berlin round may 1st 😉

Photo credit: 96dpi / CC BY-NC

  1. May 3, 2013 at 21:42

    I love the picture 🙂

  2. SithMaster
    July 30, 2013 at 02:45

    Did the conflict issue actually get fixed?
    It seems people using 1.3 of the client are still getting conflict file issues and I can’t seem to find a solid answer on the forums.

  3. Centrex
    August 2, 2013 at 07:47

    Apparently it did not get fixed. Owncloud 5.0.9 with Sync client version 1.3.0 (Windows 7, ubuntu and Centos clients) – generating tons of _conflict files.

    • dragotin
      August 2, 2013 at 08:11

      I hope you realize that there are valid reasons to create conflict files. If you have considered that and still have wrong conflicts I suggest to file a bug report with the relevant logs. Than we can investigate.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: