Ah, awesome, I hadn't done any real looking for fuzzing solutions yet. I'll
grab that one and at least use it to start setting up some local testing
while I'm hunting around for test data I can include. (I don't think I can
grab apache 2 licensed data and toss it into a package with the standard
Also it's probably easiest if folks have these handy to just propose an
addition to the test repository at
https://github.com/drswork/image/tree/master/testdata since sending busted
images via email is fraught with all sorts of exciting peril.
On Thursday, February 13, 2020 at 1:05:50 PM UTC-5 D
Fuzz testing is absolutely reasonable and something I want to set up once
I've got the first pass of code done.
On Thursday, February 13, 2020 at 11:42:16 AM UTC-5 jake...@gmail.com wrote:
> This may be slightly tangential, but this seems like the kind of code that
> would benefit greatly from
Specifically ones that are compatible with the Go license. The more broken
they are the better. Bonus points for ones that trigger degenerate
behaviour in the decoding libraries.
The tldr here is that I'm making a bunch of changes to the basic image
libraries to add in metadata support. Since I
