Release v3.30.1-beta.3 (#2158)

Improvements for all users:

• We updated the localizations and fixed some GUI texts which were not correctly
  localized.

See also known issues.

Happy syncing!

Release v3.30.1-beta.2 (#2157)

Improvements for all users:

• Default values will now be provided by the client for remote metadata when
  they're not provided by cozy-stack.

See also known issues.

Happy syncing!

Release v3.30.1-beta.1 (#2153)

Improvements for all users:

• We've optimized the initial listing of documents present on the remote Cozy to
  limit the number of necessary network requests and the CPU and RAM usage. This
  should also result in a quicker listing.

Improvements for Windows and macOS users:

• The improvement introduced in the latest version around the trashing of
  complete folders (i.e. keeping their hierarchy in the Trash) would in turn
  generate visible errors in the main window and pause the synchronization until
  the remote trashing of all the documents in the folder would be fully
  synchronized.
  We're now making sure the trashing of a folder is swift and does not result in
  unnecessary errors.

See also known issues.

Happy syncing!

Better have good foundations

Improvements for all users:

• All child moves (i.e. document moved because their parent directory was moved)
  will now be notified to the GUI so the child documents paths can be updated in
  the list of recently synchronized documents.
• We've introduced a mechanism to detect dependencies between multiple changes
  on the same side (i.e. the local filesystem or the remote Cozy) and
  synchronize them in the right order. We've added a few dependencies that let
  us solve situations that were known to fail (e.g. trashing directories as a
  whole instead of trashing every element separately) and we will add more as
  needed in the future.
• As stated above, directories will now be trashed as a whole but we'll now also
  keep empty directories in the trash instead of erasing them. It should be
  easier for you to find deleted elements in the trash and restore entire
  directories.
• We've decided to stop linking a local and remote directories at the same
  location during the synchronization as this could lead to issues (e.g. if one
  of them was moved and the other created).
  We'll handle this situation as a conflict instead.
• When propagating documents to the remote Cozy, we should now always use the
  correct parent directory which is not necessarily the remote folder with this
  path.
• The propagation of documents to the remote Cozy should now be slightly faster
  as we make fewer requests to the remote Cozy (i.e. we don't look for the
  parent directory on the remote Cozy anymore).
• Name conflicts detected during the synchronization phase will now be notified
  to you within the main window. Their resolution will only happen on your
  behalf via the action button within the error message.
• URLs entered during the client's Onboarding won't be considered as invalid if
  they contain a port but not the http protocol and will be considered as https
  URLs instead.

Improvements for Windows users:

• The detection of local overwriting moves should be more reliable. This also
  improves the propagation of remote overwriting moves to the local filesystem.
• The detection of local directory moves when they have a lot of content should
  be more reliable. This also improves the propagation of remote directory moves
  to the local filesystem.

Improvements for macOS users:

• We've fixed an issue in our local changes watcher that could lead to
  synchronizing a file deletion when actually replacing it with another one on
  the local filesystem.
• We've fixed an issue in our local changes watcher that could lead to
  synchronization errors due to invalid metadata when a file was moved then
  modified in a short period of time or modified multiple times in a short
  period of time, leaving you with a blocked synchronization until the file is
  modified, moved or removed.
• Deletions of children of moved directories while the client was stopped should
  now be correctly detected and propagated to the remote Cozy.

See also known issues.

Happy syncing!

Release v3.30.0-beta.1 (#2147)

Improvements for all users:

• All child moves (i.e. document moved because their parent directory was moved)
  will now be notified to the GUI so the child documents paths can be updated in
  the list of recently synchronized documents.
• We've introduced a mechanism to detect dependencies between multiple changes
  on the same side (i.e. the local filesystem or the remote Cozy) and
  synchronize them in the right order. We've added a few dependencies that let
  us solve situations that were known to fail (e.g. trashing directories as a
  whole instead of trashing every element separately) and we will add more as
  needed in the future.
• As stated above, directories will now be trashed as a whole but we'll now also
  keep empty directories in the trash instead of erasing them. It should be
  easier for you to find deleted elements in the trash and restore entire
  directories.
• We've decided to stop linking a local and remote directories at the same
  location during the synchronization as this could lead to issues (e.g. if one
  of them was moved and the other created).
  We'll handle this situation as a conflict instead.
• When propagating documents to the remote Cozy, we should now always use the
  correct parent directory which is not necessarily the remote folder with this
  path.
• The propagation of documents to the remote Cozy should now be slightly faster
  as we make fewer requests to the remote Cozy (i.e. we don't look for the
  parent directory on the remote Cozy anymore).
• Name conflicts detected during the synchronization phase will now be notified
  to you within the main window. Their resolution will only happen on your
  behalf via the action button within the error message.

Improvements for Windows users:

• The detection of local overwriting moves should be more reliable. This also
  improves the propagation of remote overwriting moves to the local filesystem.
• The detection of local directory moves when they have a lot of content should
  be more reliable. This also improves the propagation of remote directory moves
  to the local filesystem.

Improvements for macOS users:

• We've fixed an issue in our local changes watcher that could lead to
  synchronizing a file deletion when actually replacing it with another one on
  the local filesystem.
• We've fixed an issue in our local changes watcher that could lead to
  synchronization errors due to invalid metadata when a file was moved then
  modified in a short period of time or modified multiple times in a short
  period of time, leaving you with a blocked synchronization until the file is
  modified, moved or removed.
• Deletions of children of moved directories while the client was stopped should
  now be correctly detected and propagated to the remote Cozy.

See also known issues.

Happy syncing!

Notes be notes, even with pictures

Improvements for all users:

• Cozy Notes with photos will be exported as a tar archive instead of a simple
  markdown file. Therefore, the client will now unpack the markdown file from
  the archive when displaying a note in a degraded mode (i.e. when you're
  offline or the actual note can't be found on the remote Cozy).
• Error messages will now be properly localized and the document names included
  in some of them should be properly displayed instead of their type.

See also known issues.

Happy syncing!

Release v3.29.0-beta.2 (#2132)

Improvements for all users:

• Error messages will now be properly localized and the document names included
  in some of them should be properly displayed instead of their type.

See also known issues.

Happy syncing!

Release v3.29.0-beta.1 (#2126)

Improvements for all users:

• Cozy Notes with photos will be exported as a tar archive instead of a simple
  markdown file. Therefore, the client will now unpack the markdown file from
  the archive when displaying a note in a degraded mode (i.e. when you're
  offline or the actual note can't be found on the remote Cozy).

See also known issues.

Happy syncing!

Some errors are just not meant to shine

Improvements for all users:

• The client will now detect when the connected Cozy has been deleted and will
  show an error message accordingly.
  The synchronization will be stopped until you connect your client to another
  Cozy.
• We've worked on the process which decides if a synchronization error needs to
  be displayed or not to make sure you get alerted with the suspended
  synchronization status only if accompanied with an explicit error message.
• In some rare situations where a document that was previously synchronized is
  now only present on one side (i.e. we're in the middle of re-synchronizing it)
  a conflict could be generated if the document was modified on that remaining
  side.
  We've introduced some mitigations to avoid generating those conflicts.
• Due to a "bug" in Chromium (i.e. which we use through Electron to provide our
  network stack), some error responses sent by the remote Cozy to our file
  upload requests are transformed into a cryptic error which we cannot deal with
  directly. In such cases, we end up interpreting them as unreachable Cozy
  errors which is misleading to you.
  We caught and fixed two of those cases:
  • when sending files larger than the maximum allowed by the remote Cozy (i.e.
    5 GiB for Cozies hosted by us)
  • when the amount of data sent does not match the expected file size (i.e.
    because the actual local file has grown since last we detected a change)
• We'll now consider the propagation of a move to the trash either on the local
  filesystem or the remote Cozy as successful when the given document does not
  exist anymore.
  This will prevent delays during the synchronization process since we won't
  have to deal with retries.

Improvements for Windows users:

• The last modification and last access dates on Windows were not precise enough
  for Cozy Desktop to detect sub-second local modifications. This would
  sometimes lead to Invalid metadata errors when sending modifications to the
  remote Cozy.
  We've increased this precision to include milliseconds so we should not lose
  any local modification anymore.

Improvements for macOS users:

• Moving a local document to a folder that was just renamed or moved (e.g. a
  folder that was just created with a custom name) will be properly handled and
  not generate incoherent movements.
• Some steps of the initial scan could be run twice if some local modifications
  were detected while the initial scan was still running.
  We've made sure we don't lose time of consume unnecessary computing resources
  by making sure those steps are only run for the real initial scan.

See also known issues.

Happy syncing!

Release v3.28.1-beta.4 (#2121)

Improvements for all users:

• We've realized that the errors thrown when trying to trash a missing local
  document would not always be caught because of an unexpected message
  localization.
  We've completely changed the way we catch these errors to not depend on their
  message altogether.

See also known issues.

Happy syncing!