-
-
Notifications
You must be signed in to change notification settings - Fork 812
More cases of Non-blocking parser reporting incorrect locations when fed with non-zero offset #1412
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
Labels
2.19
Issues planned at earliest for 2.19
has-failing-test
Indicates that there exists a test case (under `failing/`) to reproduce the issue
Milestone
Comments
For convenience, let's inline:
|
@dnault Thanks! I need to modify it a bit as records cannot be used 2.x tests (Java 8 baseline). |
cowtowncoder
added a commit
that referenced
this issue
Mar 19, 2025
cowtowncoder
added a commit
that referenced
this issue
Mar 19, 2025
Added tests, should make it easier to verify fix whenever some are forthcoming :) |
Fixed for 2.19.0 via #1415. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
2.19
Issues planned at earliest for 2.19
has-failing-test
Indicates that there exists a test case (under `failing/`) to reproduce the issue
Related to #531 -- it looks like there's still an offset calculation glitch when
ByteArrayFeeder.feed()
is called with a non-zero array offset.Jackson version: 2.18.3
I've attached a slightly more comprehensive unit test.
feedByteByByteFromOffsetZero()
passes, but the others fail.Thanks!
ByteArrayFeederOffsetTest.java.txt
The text was updated successfully, but these errors were encountered: