Troubleshoot Sharp corrupted image loading issue

[nathanielrindlaub]

Related to #60.

Sharp fails to load and resize images that are corrupted (errors look like VipsJpeg: Corrupt JPEG data: 18 extraneous bytes before marker 0xd2) - which happens a lot with wireless cameras. Typically it's just a pixel or two that is missing so the images still have a lot of information and value, and a lot of other photo apps have no problem opening them.

It looks like Sharp has a setting to relax when it fails (see options.failOn here). Look into this and experiment.

[nathanielrindlaub]

Options to pass to failOn, copied from from Sharp docs:

when to abort processing of invalid pixel data, one of (in order of sensitivity): 'none' (least), 'truncated', 'error' or 'warning' (most), higher levels imply lower levels, invalid metadata will always abort.

e.g.:

// play around with 'none', 'truncated', etc. with various different corrupted images we've encountered to see what happens
await sharp(path.join(this.tmp_dir, md.FileName), { failOn: 'none' })
            .resize(dims[0], dims[1], {
                fit: 'inside'
            })
            .toFile(tmp_path);