perf(deleteAction): Queue delete requests

[nfebe]

When multiple files are deleted at once, all the requests bombard the server simultaneously, causing performance issues.

This commit adds queuing that limits the concurrency of these requests to 5 at a time.

---

Without Queuing

With Queuing

Resolves : #45234

[joshtrichards]

Certainly an improvement, but since this is all browser side aren't we creating a new problem: i.e. if the browser is closed before the entire delete session finishes?

Maybe we go farther and add the full item list to a new background job handled server-side? We already expire the trash contents in a background job so...

Perhaps more appropriate in a future follow-up (if the browser being closed aborting the delete queue is considered acceptable for now).

[susnux]

Maybe we go farther and add the full item list to a new background job handled server-side? We already expire the trash contents in a background job so...

I do not know any WebDAV standard allowing bulk delete so this would need a custom API so definitely a thing we need to think through.

[susnux]

/compile

[solracsf]

Certainly an improvement, but since this is all browser side aren't we creating a new problem: i.e. if the browser is closed before the entire delete session finishes?

What about adding a word on the already exitsting message like:

Bulk delete in progress, please keep this window open in your browser

Could this be a thing?

[nfebe]

@solracsf I tracked your concerns here : #45281 I think we can manage fix it from there.

[nfebe]

/compile

[artonge]

/backport to stable29

[artonge]

/backport to stable28

[artonge]

/backport to stable27

[nfebe]

/compile

[backportbot]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b backport/45237/stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 23c71bd8 21a22a39 18f5507e

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45237/stable27

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[artonge]

/backport to stable27

[backportbot]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b backport/45237/stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 23c71bd8 21a22a39 18f5507e

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/45237/stable27

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!