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'm in there anyway I figure I may as well add in some safety measures against files that consume an unreasonable amount of time and/or space to decode. (Or encode if anyone's got an image.Image that triggers bad behaviour) Having a good suite of known-bad files to check against will be handy to make sure the code actually works which is, y'know, kinda nice. (I am aware of some bad files kicking around the web, and I've grabbed some for testing, but none I've run across so far have licenses on them that'd allow me to toss them up on github as part of the tests for this stuff. Hence the asking around) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a0555b8b-f9c9-48a0-9649-1a835b144f4a%40googlegroups.com.
