File upload to share of external storage local / copy step after complete
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
The file upload from the browser to the share is chunked and responsive, but at the end there is the merge(? zusammenführen) step which just blocks (and may cause timeouts) in which the complete file is copied to its final destination. Which can take a while for "huge" (>=10GByte) files.
I mean its literally a local path, why cant the part file be created and written in its final destination while the upload is happening?
Tidy up reasons if something fails?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the browser upload flow through chunk merging and the copy to the final external-storage destination; the issue does not name specific files or tests. Determine whether writing directly to the final local path is supported and how failures should clean up partial files. Done means large uploads avoid the blocking copy step without leaving untidy partial files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100