cozy-desktop

Improvements for all users:

• We've updated again some of our dependencies that don't require changes in
  our code. Those are the same that were upgraded in v3.13.1-alpha.1
  then downgraded back in v3.13.1-beta.1.
  We investigated, identified and excluded the problematic updates, so
  networking should work as expected this time.

See also known issues.

Happy syncing!

Improvements for GNU/Linux users:

• We've mitigated an issue LibreOffice users could encounter while saving.
  LibreOffice uses an intermediary temporary file when saving and in some
  situations we could end up deleting the file altogether or move the previous
  version to the Cozy's trash and even not be able to synchronise the new
  version.
  We're now ignoring those temporary files (i.e. with extension .osl-tmp)
  which results in a correct update of the office document.

Improvements for all users:

• The solution above applies only to LibreOffice users on Linux while there are
  other software saving through a temporary file.
  We are now able to detect the use of a temporary file in some situations and
  correctly handle it (i.e. not move it to the trash and synchronise the new
  version).

There are some known issues that we'll tackle in the next releases:

• When we don't detect any update closely following the temporary file deletion
  and that file is not ignored, we end up deleting the file that was saved.
  This is a more general situation and should be fixed very soon.

See also known issues.

Happy syncing!

Improvements for MacOS users:

• We recently introduced a new icon for the Disconnected app status when we
  can't reach your remote Cozy. On MacOS, this icon was rendered incorrectly
  within the app itself, in the status bar.
  We changed the icon to be of the expected color in the systray and the app
  status bar.

Changes that should have no effects:

• We did some minimal refactoring on our proxy setup to introduce some tests.
  There should be no effects on the way the proxy works.

See also known issues.

Happy syncing!

Improvements for all users:

• We added a new icon set for the Offline status. Prior to this version,
  whenever we detected you might be disconnected from the Internet, we would
  display a "pause" icon with the "Disconnected" status label. We're now
  displaying a shadowed version of the main icon and a "No Internet connection"
  status label. We hope this is clearer to you.
• We fixed a bug in the way we sort changes coming from your remote Cozy. For
  some changes like the replacement of a file, the order in which we receive
  changes from the remote Cozy is crucial to applying it correctly on the local
  filesystem. In this particular case, we were not always sorting correctly the
  deletion and recreation of the file (or folder) which could lead to documents
  disappearing or conflicts to appear.

See also known issues.

Happy syncing!

Improvements for Windows & GNU/Linux users:

• When renaming folders and deleting part of their content while the client
  was stopped, the deletion should now be properly handled on restart.

Improvements for all users:

• We downgraded the dependencies upgraded in v3.13.1-alpha.1
  because the upgrade broke networking. It should work again now.

See also known issues.

Happy syncing!

Improvements for contributors:

• We've decided to run prettier over our entire codebase with the cozy-app
  eslint config and to keep using it from now on. This will remove the need to
  check for syntax errors and improve homogeneity between Cozy Cloud javascript
  projects.

Improvements for all users:

• We've updated some of our dependencies. There shouldn't be any consequence but
  it's just good hygiene and could potentially fix issues we don't even know.

See also known issues.

Happy syncing!

Improvements for Windows and GNU/Linux users:

• We completely revamped the local watcher (the component looking for changes
  in your local Cozy Drive directory). It should now be faster and more
  reliable when synchronizing live changes. Expect a few more optimizations
  regarding the initial scan very soon.
• The watcher type used (i.e. atom or chokidar) can still be chosen via the
  config file. The new watcher (atom) is the default on Windows and GNU/Linux.

Improvements for all users:

• We've updated our icons to reflect the new Cozy branding with a deep blue
  instead of the faded one and more of that blue around our lovely little cloud.
• The remote watcher now ignores changes with a revision lower than the one
  we've saved on the associated document in the local Pouch. Failing to do so
  was leading to files disappearing locally (before reappearing a short while
  later) during their upload to the Cozy. This could also be the cause of
  unexpected and undocumented behavior.
• Since it could be surprising and even misleading, we've removed the count of
  the remaining items to be synchronised until we can be sure it's always
  accurate. In the meantime, you'll see a simpler message indicating the client
  is syncing.
• We fixed an issue we had in the generation of a conflict file name
  where the conflict suffixes could be added indefinitely in case the
  conflicting file would get in conflict again. It happened that directories or
  files without an extension were still subject to a similar issue.
  We made sure they will only ever have one conflict suffix added to
  their name even in case they get in conflict again.
• During the synchronisation process, a document can change either locally
  (e.g. its checksum has changed because of a modification) or on the Cozy
  (e.g. the file was moved or modified by another client). In this situation the
  Cozy won't accept the change and will answer with an error. When we receive
  errors from the Cozy we retry up to 3 times to apply the change but if the
  document has changed, we will never be able to apply it and will only lose
  time by retrying.
  We now retry only on network and disk space errors to speed up the
  synchronisation of files rapidly changing.
• Files and folders named like a volume (e.g. C:) and at the root of the folder
  watched by Cozy Desktop could lead to an infinite loop if they or any of their
  children were ever modified. Those are now handled properly and won't be
  ignored either.
• Fixed a race condition case were a sharing could be disabled when a folder
  was moved locally while another one was added remotely to the same
  destination.
• We updated one of our main dependencies, Electron, to its 2.x version. We are
  still not using the latest version but this one brings us back support from
  the Electron team and security fixes. Other updates will come in the following
  releases.

See also known issues.

Happy syncing!

Improvements for Windows and GNU/Linux users:

• We fixed the last known issue regarding files and directories renamed while
  the client is stopped using the new watcher. The next release should be a
  stable one! 🚀

See also known issues.

Happy syncing!

Improvements for all users:

• The remote watcher now ignores changes with a revision lower than the one
  we've saved on the associated document in the local Pouch. Failing to do so
  was leading to files disappearing locally (before reappearing a short while
  later) during their upload to the Cozy. This could also be the cause of
  unexpected and undocumented behavior.

Improvements for MacOS users:

• When updating the Cozy branding, we messed up the alignment of icons in the
  MacOS installer. The Cozy app icon, the arrow and the Applications folder are
  now properly aligned and vertically centered in the installer window.

See also known issues.

Happy syncing!

Improvements for all users:

• We've updated our icons to reflect the new Cozy branding with a deep blue
  instead of the faded one and more of that blue around our lovely little cloud.

Improvements for Windows and GNU/Linux users:

• With our new watcher, some remote movements that were detected, taken into
  account but not applied locally (i.e. the file or directory itself would not
  have been moved on the filesystem) because the client was stopped in the
  middle of the synchronisation process would not be correctly applied after the
  client is relaunched. In this situation, we would end up duplicating the
  document that was moved, at its previous path.
  We made sure we detect unapplied remote movements so we can finish applying
  them and not duplicate your documents.
• Since it could be surprising and even misleading, we've removed the count of
  the remaining items to be synchronised until we can be sure it's always
  accurate. In the meantime, you'll see a simpler message indicating the client
  is syncing.

See also known issues.

Happy syncing!

Improvements for Windows and GNU/Linux users:

• We now detect and correctly synchronise file moves where the destination
  already existed and is being overwritten.
  However since filesystems and file browsers are all different, you might
  have a different experience on Linux. We made sure this works with the
  GNOME file browser, Nautilus.
• We improved the way we aggregate quick modifications to files to avoid
  having to synchronise a lot of changes when we only care about the result
  of the last one.

See also known issues.

Happy syncing!

Improvements for Windows and GNU/Linux users:

• We recently fixed an issue we had in the generation of a conflict file name
  where the conflict suffixes could be added indefinitely in case the
  conflicting file would get in conflict again. It happens that directories are
  still subject to a similar issue.
  We made sure directories will only ever have one conflict suffix added to
  their name event in case they get in conflict again.
• During the synchronisation process, a document can change either locally
  (e.g. its checksum has changed because of a modification) or on the Cozy
  (e.g. the file was moved or modified by another client). In this situation the
  Cozy won't accept the change and will answer with an error. When we receive
  errors from the Cozy we retry up to 3 times to apply the change but if the
  document has changed, we will never be able to apply it and will only lose
  time by retrying.
  We now retry only on network and disk space errors to speed up the
  synchronisation of files rapidly changing.

See also known issues.

Happy syncing!

Improvements for Windows and GNU/Linux users:

• Rapid successive changes on the same file were possibly generating conflicts
  because the new watcher was messing up with the changes propagation. There
  were actually 2 underlying issues behind this: one that was specific to the
  new watcher and another that was not. We actually fixed both, although the
  second one was not supposed to happen anymore once the new watcher would
  behave correctly, but could still have been uncovered during upcoming
  optimizations.

See also known issues.

Happy syncing!

Improvements for Windows users:

• With the new local watcher, we introduced a more precise way to identify files
  and folders on the filesystem. To make sure previously detected documents
  benefit from this new identification we need to migrate all of them when we
  get the new identifier. This version takes care of the migration in a way that
  avoids running a full synchronisation when we only change the identifier as it
  has value on the local client only.

There are some known issues that we'll tackle in the next releases:

• On Windows, moving a tree of directories and files to a destination that
  shares part of this tree (e.g. src/dir/subdir/file → dst/dir/subdir/file)
  and overwriting the destinations will result in conflicts being created for
  the overwritten files.
• On Windows, the synchronisation of a remote move stopped before it's been
  applied on the local system will won't be resumed when restarting the client.
• On Linux, some movements done while the client was stopped won't be correctly
  detected and handled when starting the client.

See also known issues.

Happy syncing!

Improvements for Windows and Linux users:

• The new local watcher is now the default watcher. It should bring better
  performance in local changes analysis.
• We found a bug in the synchronisation process of directories that could lead
  to missed updates. We have not seen any reports of it but the mechanism has
  been fixed anyway.
• We updated one of our main dependencies, Electron, to its 2.x version. We are
  still not using the latest version but this one brings us back support from
  the Electron team and security fixes. Other updates will come in the following
  releases.

Improvements for Windows users:

• Files and folders named like a volume (e.g. C:) and at the root of the folder
  watched by Cozy Desktop could lead to an infinite loop if they or any of their
  children were ever modified. Those are now handled properly and won't be
  ignored either.

There are some known issues that we'll tackle in the next releases:

• On Windows, moving a tree of directories and files to a destination that
  shares part of this tree (e.g. src/dir/subdir/file → dst/dir/subdir/file)
  and overwriting the destinations will result in conflicts being created for
  the overwritten files.
• On Windows, the synchronisation of a remote move stopped before it's been
  applied on the local system will won't be resumed when restarting the client.
• On Linux, some movements done while the client was stopped won't be correctly
  detected and handled when starting the client.

See also known issues.

Happy syncing!

Improvements for Windows users:

• Changing only the case of a file/directory name now works as expected when
  using the new watcher.

See also known issues.

Happy syncing!

Improvements for Windows and Linux users:

• Successive moves (e.g. A → B → C → D) are now correctly applied (i.e. A → D)
  with the new local watcher.
• The introduction of the new local watcher brought a performance regression
  during the initial Cozy directory scan. We ported an optimisation we had in
  the previous watcher to the new one which should make the initial scan phase
  about 3x faster.
• We found a bug in the synchronisation process of directories that could lead
  to missed updates. We have not seen any reports of it but the mechanism has
  been fixed anyway.
• We updated one of our main dependencies, Electron, to its 2.x version. We are
  still not using the latest version but this one brings us back support from
  the Electron team and security fixes. Other updates will come in the following
  releases.

Improvements for Windows users:

• Moves from a directory that has just been moved to a path outside this
  directory will now be correctly detected and applied with the new local
  watcher.

There are some known issues that we'll tackle in the next releases:

• On Windows, moving a tree of directories and files to a destination that
  shares part of this tree (e.g. src/dir/subdir/file → dst/dir/subdir/file)
  and overwriting the destinations will result in conflicts being created for
  the overwritten files.
• On Windows, the synchronisation of a remote move stopped before it's been
  applied on the local system will won't be resumed when restarting the client.
• On Linux, some movements done while the client was stopped won't be correctly
  detected and handled when starting the client.

See also known issues.

Happy syncing!

Improvements for Windows and Linux users:

• The new local watcher is now the default watcher. It should bring better
  performance in local changes analysis.

Improvements for Windows users:

• Files and folders named like a volume (e.g. C:) and at the root of the folder
  watched by Cozy Desktop could lead to an infinite loop if they or any of their
  children were ever modified. Those are now handled properly and won't be
  ignored either.

There are some known issues that we'll tackle in the next releases:

• On Windows, moving the child of a moved directory won't be handled properly.
• On Windows, moving a tree of directories and files to a destination that
  shares part of this tree (e.g. src/dir/subdir/file → dst/dir/subdir/file)
  and overwriting the destinations will result in conflicts being created for
  the overwritten files.
• On Windows, the synchronisation of a remote move stopped before it's been
  applied on the local system won't be resumed when restarting the client.
• On Linux, some movements done while the client was stopped won't be correctly
  detected and handled when starting the client.

See also known issues.

Happy syncing!

Improvements for Windows and Linux users:

• The watcher type used (i.e. atom or chokidar) can now be chosen via the config
  file. This means the new watcher will be testable easily with any version of
  the app starting from now.

See also known issues.

Happy syncing!

Improvements for all users:

• Fixed a race condition case were a sharing could be disabled when a folder
  was moved locally while another one was added remotely to the same
  destination.

Improvements for Windows and Linux users:

• The right path separator is now used while squashing successive events (e.g.
  file added or updated, then moved immediately) in the new watcher.

See also known issues.

Happy syncing!