Handling unprocessable assets

[donaldgray]

During testing Orchestrator with Cantaloupe using Grok on the dlcs development environment I came across a couple of images that returned a 501 / Not Implemented.

Both of the items in question look to have been direct uploads via the Portal or API as they are stored in the origin-bucket. IIP has no issues processing these so it's maybe a Grok issue rather than Cantaloupe.

This ticket is to ensure we revisit these to clarify how to handle them and whether this affects Kakadu and/or OpenJpeg processor too.

The assets that caused issues were:

• 8/1/002-Index-A-B-1760-1762-Mass-SJC.jp2
• 8/1/001-Cover-1760-1762-Mass-SJC.jp2

[donaldgray]

Possibly related to dlcs/image-server-node-cantaloupe#7

[donaldgray]

Closing for now - 501 / Not Implemented seems to be result of issue with JP2 processor. Also seeing issues where JP2 processor failing can result in an empty 200 response (0-byte length), only seen with Grok so far but can be tracked by issue above.

Regarding the 2 issues in original ticket, these are resolved by upgrades made in: dlcs/image-server-node-cantaloupe#9