Closed bwaldron closed 3 years ago
It's not you, it's me. I forgot to add an integration test for this command. I'm working on a fix, but currently our release system is down (TravisCI OS X builds have stopped working), so we're in the middle of migrating to a new release system based on Github Actions. So it could be 1-2 weeks.
I understand and appreciate the heads up, is it isolated to trim.threshold? We use the ImageResizer querystring methods currently and are comfortable with the items that your team documented that aren't supported going forward.
It's isolated to the whitespace trimming feature, yes.
On Wed, Dec 9, 2020, 10:33 PM Ben Waldron notifications@github.com wrote:
I understand and appreciate the heads up, is it isolated to trim.threshold? We use the ImageResizer querystring methods currently and are comfortable that your team documented that aren't supported.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/imazen/imageflow-dotnet/issues/24#issuecomment-742251608, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2LHZJHLYCLXOMH3GXN4DSUBMTVANCNFSM4UUIKAKA .
This is now fixed.
Update NativeRuntime to 1.5.4 and this should be working again.
Imageflow.Net (0.7.19) Imageflow.NativeRuntime.win-x86_64 (1.5.3-rc57)
In going from ImageResizer to ImageFlow, we are seeing exceptions within white space trimming only with resize and other querystring operations working as documented. I am likely missing something obvious, but wanted to see if there is an underlying bug.
For example, with a any valid image all of the following will result in the same error: