Error reporting for filesystem matters
Open
Nobody has claimed this yet.
enhancement
feature: backups
feature: deletion
feature: download
feature: extraction
feature: integrity
feature: moving
overview
robustness 💪
UX🙂
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
For an improved user experience (and the reduction of invalid bug reports) we should add better interpretation (i.e. errno to readable hints) and reporting of underlying errors (at least as reported to us by the underlying OS) in the following steps/areas:
- createBackup()
- downloadUpdate()
- extractDownload()
- verifyIntegrity()
- moveNewVersionInPlace()
- deleteOldFiles()
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 locating the implementations of createBackup(), downloadUpdate(), extractDownload(), verifyIntegrity(), moveNewVersionInPlace(), and deleteOldFiles(). Inspect how each currently handles underlying filesystem failures and check any related tests. Done means these steps report OS errors with readable errno hints, but the issue does not define exact wording or test files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100