Enhancement: improve input file error messaging
- Dominant language
- JavaScript
- Stars
- 32.7k
- Forks
- 1.4k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 5
Description
libvips and sharp currently only check an input file is missing (ENOENT) but could probably check for and differentiate on EACCES and perhaps other less common errors such as ELOOP etc.
https://github.com/libvips/libvips/blob/5df173dd15f5acc809690f0cfc427f4d077edbab/libvips/iofuncs/util.c#L1107-L1112
See https://github.com/lovell/sharp/issues/1919#issuecomment-549173298
(ACL stuff on Windows can be tricky so needs testing.)
Contributor guide
Research direction
Start by reading the referenced libvips util.c lines 1107-1112 and the discussion in sharp issue 1919. Trace how sharp reports missing input files, then investigate handling for EACCES and other errors, including Windows ACL testing. Done means input-file failures are differentiated without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100