New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression: PNG which parsed in 0.16 fails to parse in 0.17 #337
Comments
Issue being that https://github.com/image-rs/image-png/blob/master/src/decoder/stream.rs#L628-L640 This discards some of the head of a chunk larger than that constant (see |
Is there a way to opt out of the tEXT decoding entirely for now, perhaps to just turn off that feature if you don't need it? |
I'm afraid not. I'll have a fix soon and in the long term this makes sense. Can I utilize the provided image as a regression test, provided that I'll be replacing the pixel data with some dummy chunk? Otherwise a synthetic one will also do but real world data is always better. |
Please do so! |
That means you do have any authority to permit this? I'm certainly not adding files with unclear copyright/licensing status to the repository. The good news is that with #338 applied all files in that archive pass:
|
Not necessarily - that account is one of our customers and we're using these files for QA testing. Our QA person said that they are free for non commercial use, but now that you mention it, I can't find a license either; I'll try to clear that up and report back. |
Ok so I just found this: https://www.caeora.com/content-use |
Is there any chance for a minor release with this patch? |
@Follpvosten Quite likely, I'm just waiting to see if #333 will also land in time. Release likely within the next few days in any case. Remind me if not 😉 |
During QA testing this issue came up.
I have a full example which reproduces it here: https://github.com/Follpvosten/png-parse-regression
Basically, the standard example from the docs used to decode this PNG fine. In 0.17, it doesn't work anymore.
The example I wrote has two tests which confirm that.
I have other example files which fail to parse if that's useful, and if I can do anything else to help with this issue, please let me know.
We won't be able to use 0.17 (and thus image 0.24) in production until this is fixed.
The text was updated successfully, but these errors were encountered: