Bulk Upload Issues

[mgallien]

When implementing the client side of the new bulk upload protocol I found a few issues with it:

• The type of checksum is enforced to be MD5 only. Would be nice to get the usual mechanism when server announces what is supported and desktop client then indicate the chosen type;
• The error reporting is missing details (with plain WebDAV it is possible to get more details about error handling). I guess I will then force files in error to be uploaded via plain old WebDAV.

Reported issues:

• Bulk Upload - Deadlock found when trying to get lock #29985
• Bulk Upload - Computed md5 hash is incorrect #29984
• Sabre\DAV\Exception Unknown error while seeking content upload error leads to client freeze #30424
• Timestamp issue with Nextcloud 23.0 #30473
• [Bug]: InvalidArgumentException: X-OC-MTime header must be a valid positive integer #31464
• [Bug]: Prevent upload of file wih invalid characters via bulk upload #37213
• Bugfix/bulk upload empty files #39221
• fix(dav): Improve handling and logging of bulk upload failures #42001
• Improve bulk upload and add a config switch for it #33697
• Fix ETAG returned by bulk upload #33659
• Set the file's mtime from the headers in bulk upload #30485

Might have more later but apart from that works nicely.

[mgallien]

@artonge sorry for the delay but as discussed a few small issues with bulk upload

[mgallien]

I have another issue.
To speed up the upload I tried to send another request after sending the first one but before getting the reply of the first one.
Most of the time I get errors reported about locking issues.
It would really increase the speed if from desktop client perspective more than one request could be done at a time.

[solracsf]

Maybe also related: #31464

[brainchild0]

I would suggest the addition of #23615.

The issue has been closed, but I would characterize it as still unresolved, and as such, I feel it should remain open.