Automatically clean-up leftover `.part` files after failed uploads to shared folders
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Steps to reproduce
- Create a link share for a folder with File Drop permission
- Upload files and before finish cut the connection
Expected behaviour
.part files should be automatically removed, if upload has failed.
Actual behaviour
.part file(s) remain on file system. Invisible on nextcloud, only in direct acces to the filesystem
Server configuration
Operating system:
Ubuntu 20.04
Web server:
Apache/2.4.41
Database:
mariadb 10.3.25
PHP version:
7.4.3
Nextcloud version:
20.0.8
Updated from an older Nextcloud/ownCloud or fresh install:
updated
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
local
Are you using encryption: yes/no
no
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 File Drop upload handling for shared folders and reproduce the interrupted upload described in the issue. Check how failed uploads leave .part files on the local filesystem. Done means interrupted uploads clean up their leftover .part files without affecting completed uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100