Skip to content

fix(nextcloud): serialize multi-file uploads to avoid proxy failures - #30

Open
LeonardNJU wants to merge 1 commit into
bulwarkmail:mainfrom
LeonardNJU:fix/nextcloud-sequential-file-uploads
Open

LeonardNJU wants to merge 1 commit into
bulwarkmail:mainfrom
LeonardNJU:fix/nextcloud-sequential-file-uploads

Conversation

@LeonardNJU

Copy link
Copy Markdown

Summary

  • Serialize files selected from the Nextcloud Files page instead of starting all transfers concurrently through the Bulwark plugin proxy.
  • Queued uploads can be cancelled and later resumed without duplicate starts.
  • Add regression tests for sequential multi-file upload and queued cancel/resume.

Motivation

On a self-hosted Bulwark 1.17.0 and Nextcloud 33 deployment running Nextcloud plugin 1.1.1, choosing three small files caused only one to reach Nextcloud (WebDAV PUT 201). The other two displayed a connection error and did not reach the Bulwark proxy.
The affected user confirmed that uploads work after deploying a sequential-queue patch. This avoids bursts of browser-to-proxy uploads, although the precise transport failure is not yet established.

Verification

  • npm test -- --run nextcloud: 129 passing tests
  • npm run check: 25 plugins checked successfully
  • git diff --check: clean

Only source and tests are changed. No credentials or generated artifacts included.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant