Merged
Conversation
This reverts commit f86ad8b.
This was referenced Mar 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
libavif 1.4.0 has been released - https://github.com/AOMediaCodec/libavif/releases/tag/v1.4.0
This means that #9413 can be reverted.
I increased the epsilon for image comparison in
test_write_rgb. More interestingly though, I found thattest_encoder_advanced_codec_optionswas failing. I checked in AOMediaCodec/libavif#3088, and yes, the change in behaviour of the advanced codec options was deliberate. However, the purpose of the test is just to check that ANY advanced codec option works, so I've changed it to a different option.