-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Arrow] Fix segfault in appending list data #8042
Conversation
80a28bf
to
23e15b0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
… the arrow conventions
Thanks! |
@Mytherin |
Oh whoops - I thought the only CI failure here was the flaky test in #8074. It seems there is also a failure in CodeCov now. Could you have a look and submit a follow-up PR that fixes those? |
Sure, but I touched none of those files I could "fix" the coverage by removing this feature...Tishj:duckdb:arrow_record_batch_segfault Because it's not used anywhere |
Yes but this PR removes code that uses the validity mask in a certain way, which is likely not used anywhere else. I think that is likely why the coverage dropped |
I came across this bug while investigating some memory usage issues with record batches
The first batch always completes fine, but in subsequent batches we apply the Slice again which is a problem, in
ArrowScalarBaseData::Append
auto source_idx = format.sel->get_index(i);
gives us back random uninitialized memory.