Skip compressed file SAX test on libxml2 >= 2.15#3602
Merged
flavorjones merged 1 commit intomainfrom Feb 17, 2026
Merged
Conversation
flavorjones
force-pushed
the
flavorjones/compression-support
branch
2 times, most recently
from
8b8f676 to
b9bf7c5
Compare
flavorjones
changed the title
libxml2 2.15.0 requires callers to explicitly pass XML_PARSE_UNZIP to enable decompression. Until Nokogiri adds support for this option, skip the test on affected versions. Closes #3599
flavorjones
force-pushed
the
flavorjones/compression-support
branch
from
b9bf7c5 to
93ecc2b
Compare
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
1 participant
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.
What problem is this PR intended to solve?
libxml2 2.15.0 removed automatic decompression — callers must now explicitly pass
XML_PARSE_UNZIPto enable it. Until Nokogiri adds support for this option, skip the compressed file SAX test on libxml2 >= 2.15.Closes #3599
Have you included adequate test coverage?
Existing coverage is sufficient.
Does this change affect the behavior of either the C or the Java implementations?
N/A