Skip to content

Release v3.26.0-beta.1 (#2046)

Pre-release
Pre-release
Compare
Choose a tag to compare
@taratatach taratatach released this 03 Mar 11:27
053ddff

Improvements for all users:

  • Files that were modified then trashed on your Cozy before the Desktop client
    could fetch the modification will be trashed on your computer and your Cozy
    and not re-uploaded.
  • The workaround we introduced in the previous release to help synchronize
    modifications to your remote Cozy when modification dates are not the same in
    the local database and the remote Cozy created a regression for users who
    locally modified documents that had not been modified in a very long time and
    did not have the remote modification date stored in the local database.
    For those documents, we'll skip the workaround and hope that the local
    modification date is more recent than the remote one (which is very likely).
  • If some of your documents (files like directories) have local names starting
    or ending with white-spaces, the client would remove those spaces when sending
    them to your remote Cozy thus creating a de-synchronized state between their
    local and remote versions. This would prevent the client from finding their
    remote version in later requests.
    We're now making sure their names are not modified when sending them to your
    remote Cozy.
  • Because of a limitation in Electron v7+, we would not be able to advertise the
    size of a file being uploaded to your remote Cozy, preventing it from refusing
    the upload right away if the file was too large or not enough disk space was
    available on the Cozy. In those cases, the client would thus send the whole
    file to see it refused by the Cozy.
    The Cozy can now receive the file size via a request parameter which allows us
    to work around the Electron limitation and get feedback on the upload from the
    very beginning thus saving time and resources.
  • In the previous release, we started managing and sometimes displaying
    synchronization errors within the client's interface but we grouped a lot of
    data and metadata related errors together as an "Unreachable Cozy" state. This
    lead to a lot of confusion as the Cozy was most of the time perfectly
    reachable and the underlying issues would not be solved.
    We now try to manage most of those errors as best we can and provide ways to
    solve the underlying issues either automatically or by notifying you.

See also known issues.

Happy syncing!