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

Output of ipc::reader::tests::projection_should_work fails validation #1548

Closed
Tracked by #1546
alamb opened this issue Apr 12, 2022 · 0 comments · Fixed by #1573
Closed
Tracked by #1546

Output of ipc::reader::tests::projection_should_work fails validation #1548

alamb opened this issue Apr 12, 2022 · 0 comments · Fixed by #1573
Labels
arrow Changes to the arrow crate bug

Comments

@alamb
Copy link
Contributor

alamb commented Apr 12, 2022

Describe the bug
The force_validate check added in #1546 reveals that some array created as part of projection_should_work test fails validation.

It is not clear if the validation is incorrect or something about ipc

To Reproduce
Uncomment the

    #[cfg(not(feature = "force_validate"))]

And then run the test like:

cargo test --features=force_validate -p arrow

lines for the following tests and the will fail:

---- ipc::reader::tests::projection_should_work stdout ----
thread 'ipc::reader::tests::projection_should_work' panicked at 'called `Result::unwrap()` on an `Err` value: InvalidArgumentError("Last offset 251658240 of List(Field { name: \"item\", data_type: Int32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: None }) is larger than values length 15")', arrow/src/array/data.rs:301:34

Expected behavior
The tests should pass when force_validate is on

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant