Alex Grebenyuk

The decoding happens using `ImageDecoding` objects. I suggest adding the decryption step during that stage, and then invoking the built-in decoders. See https://kean-docs.github.io/nuke/documentation/nuke/image-decoding for more information.

> Failed to decode image data using decoder Nuke.ImageDecoders.Default even though I can check with the debugger that the default decoder can in fact decode the image. The code that...

Hi, @mtrezza. Thanks for raising this issue, it is something I overlooked. In case the only difference is the "extent", I think adding an option to the existing processor should...

Are there any messages in the console from Core Image aside from the stack trace? I found similar crash reports online https://github.com/pinterest/PINRemoteImage/issues/109, but so far no solutions.

By default, `ImagePipeline` allows up to two images processing operations to run in parallel (`self.imageProcessingQueue.maxConcurrentOperationCount = 2`). All the processors must be thread safe. When I was working on these...

Hi, @mtrezza. Did you receive any updates from Apple regarding this issue?

Hey, @mtrezza. I would appreciate if you could add a "clamp to extent" option to the existing `GaussianBlur` processor.

Since it appears to be a Core Image bug, I'm going to close it. If you have other idea, please let me know.

Cool, makes sense. I will appreciate a pull request. I'm using this processor myself, so the help is welcome. If not, I can test and merge it later myself. Thanks.

I temporarily reverted this change in [v12.7.1](https://github.com/kean/Nuke/releases/tag/12.7.1).