Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support and document how to configure sharp to fail when loading corrupt images

See original GitHub issue

Currently, sharp will only emit a warning for corrupt images. It’d be great to add an option to sharp to support rejecting the loading of these images.

See https://github.com/lovell/sharp/issues/607#issuecomment-298678935 and https://github.com/lovell/sharp/issues/607#issuecomment-298692269 for background.

(as always, thanks for Sharp! 👍

Issue Analytics

State:
Created 6 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

2reactions

lovellcommented, Jan 12, 2018

sharp v0.19.0 now available, thanks for your work on this.

1reaction

jcupittcommented, Aug 29, 2017

With 8.5 head I now see:

john@kiwi:~/pics$ head -c 2000 k2.jpg > x.jpg
john@kiwi:~/pics$ vips copy x.jpg y.jpg
(vips:19972): VIPS-WARNING **: read gave 2 warnings
(vips:19972): VIPS-WARNING **: VipsJpeg: Premature end of JPEG file
john@kiwi:~/pics$ echo $?
0
john@kiwi:~/pics$ vips copy x.jpg[fail] y.jpg
(vips:20028): VIPS-WARNING **: error in tile 0 x 8
VipsJpeg: Premature end of JPEG file
john@kiwi:~/pics$ echo $?
1

I’ll add a test to the new libvips test suite as well.

I think you could have got an error from libjpeg with --fail, but it would have been rather difficult.