-
Notifications
You must be signed in to change notification settings - Fork 21
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
Missing UTF-32 charset should fail only in case UTF-32 is detected #121
Comments
danielkec
added a commit
to danielkec/parsson
that referenced
this issue
Jan 17, 2024
danielkec
added a commit
to danielkec/helidon
that referenced
this issue
Jan 17, 2024
This was referenced Jan 17, 2024
danielkec
added a commit
to helidon-io/helidon
that referenced
this issue
Jan 18, 2024
* #8195 JSON unicode detection workaround for eclipse-ee4j/parsson/issues/121
lukasj
pushed a commit
that referenced
this issue
Jan 23, 2024
@lukasj This issue was fixed in January, but wasn't released as I can see. Is it possible to create the new version with this fix? |
@Captain1653 if you have a question, use new issue/mail/discussion post for it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now UTF-32 chaset is looked up for unicode version detection during class initialization, no matter whether there will be ever any use of it:
parsson/impl/src/main/java/org/eclipse/parsson/UnicodeDetectingInputStream.java
Lines 32 to 35 in 981cd2f
Actual lookup should be done lazily when UTF-32 is actually detected to support runtimes without UTF-32, like GraalVM native image oracle/graal/issues/1294
The text was updated successfully, but these errors were encountered: