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

tests: handle upstream libxml2 returning null for UTF-8 enc handler #3271

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

flavorjones
Copy link
Member

@flavorjones flavorjones commented Jul 3, 2024

What problem is this PR intended to solve?

Example failure: https://github.com/sparklemotion/nokogiri/actions/runs/9774049613/job/26981486984

Let's just work around it in the tests. The behavior we're testing isn't specific to UTF-8, so let's just swap in ISO-2022-JP.

GNOME/libxml2@6d8427dc

Tagging @nwellnhof just for awareness.

Have you included adequate test coverage?

Yes

Does this change affect the behavior of either the C or the Java implementations?

N/A

Let's just work around it in the tests. The behavior we're testing
isn't specific to UTF-8, so let's just swap in ISO-2022-JP.

GNOME/libxml2@6d8427dc
@flavorjones flavorjones changed the title fix: upstream libxml2 is now returning null for UTF-8 enc handler tests: handle upstream libxml2 returning null for UTF-8 enc handler Jul 3, 2024
@flavorjones flavorjones merged commit 043e1e9 into main Jul 3, 2024
132 checks passed
@flavorjones flavorjones deleted the flavorjones-202406-libxml-encoding branch July 3, 2024 13:23
@nwellnhof
Copy link

What behavior has changed exactly in libxml2? The issue with xmlFindCharEncodingHandler should have been fixed here: https://gitlab.gnome.org/GNOME/libxml2/-/commit/c4d8343b7c56a5fd00fcd7edb8e2ceb786081570

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

Successfully merging this pull request may close these issues.

2 participants