Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-343

Drive detects corrupted binary data if a custom digest algorithm is configured server-side

    XMLWordPrintable

    Details

    • Sprint:
      Sprint Drive 7.2-6, Sprint Drive 7.2-7, Drive Next
    • Story Points:
      3

      Description

      And fails at download with:

      2015-05-04 17:11:05,964 3572 5468 DEBUG    nxdrive.engine.processor Creating local file 'MyDoc.odt' in '\\?\C:\Users\nuxeo\Documents\Nuxeo Drive\Test WS'
      2015-05-04 17:11:07,262 3572 6016 ERROR    nxdrive.engine.processor Corrupted file
      Traceback (most recent call last):
        File "nuxeo-drive-client\nxdrive\engine\processor.py", line 112, in _execute
        File "nuxeo-drive-client\nxdrive\engine\processor.py", line 440, in _synchronize_remotely_created
        File "nuxeo-drive-client\nxdrive\engine\processor.py", line 473, in _create_remotely
        File "nuxeo-drive-client\nxdrive\engine\processor.py", line 340, in _download_content
        File "nuxeo-drive-client\nxdrive\client\remote_file_system_client.py", line 102, in stream_content
        File "nuxeo-drive-client\nxdrive\client\base_automation_client.py", line 712, in do_get
      CorruptedFile: Corrupted file
      

      And more generally local and remote digest comparison is not consistent.

      Possible solution: fetch digest algorithm from server:

      • At RemoteFileSystemClient init and store it in engine configuration for use by the local client.
      • At RemoteDocumentClient init and store it in memory for use by Drive Edit.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: