Skip to content
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

Errors when decoding some image files (possibly "corrupted" by some criteria) #142

Open
inliquid opened this issue May 2, 2021 · 0 comments

Comments

@inliquid
Copy link

inliquid commented May 2, 2021

Hey!

First of all thanks for a great library, it's one of the best out there.

I'm reporting this issue just for the sake of consistency, because we first encountered this problem when run several tests with imaging and then realized that it comes from standard library. Other people may have a similar issues so I thought it would make sense to report it here as well. So feel free to close it or leave as tracking one.

Here is original issue (unexpected EOF error when reading specific file): golang/go#45902

This one is more general: golang/go#10447

Note, that a lot of software, most importantly browsers, but also editors and viewers don't treat such files as "corrupted" and decode them normally. This raises a question, which criteria should be when a library decides to skip entire file.

In our project, imaging was near perfect fit and everything was almost ready, but unfortunately we seem to have to fall back to Image Magick bindings because we have are a lot of files like this and it's hard to explain a user that his file is "corrupted" when he can open it in both browser and editor. And despite Image Magick can detect that file is not perfect it still lets decode and manipulate with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant