be more tolerant of tag read failures #320
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this can occur if the MakerNote has a pointer to outside the EXIF block
|
Seems reasonable. Might make sense to issue a warning even if Image.DEBUG isn't set. |
wiredfool
added a commit
that referenced
this pull request
Aug 21, 2013
be more tolerant of tiff tag read failures
|
Thanks |
radarhere
pushed a commit
to radarhere/Pillow
that referenced
this pull request
Sep 24, 2023
Added brotli
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am running into this issue on a file with a non-conforming MakerNote field that has a pointer to outside the EXIF block. For what it's worth, both libexif and exiv2 are more tolerant of this case by just printing an error. It seems that this situation can be very common as discussed here: http://www.exiv2.org/makernote.html