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

roaring64: container_remove_range returns null rather than returning an empty container #550

Merged
merged 1 commit into from Jan 14, 2024

Conversation

Dr-Emann
Copy link
Member

This would lead to all sorts of issues: typecode2 is read uninitialized, and hopefully just asserts that it's not one of the known typecodes. Then, we've stored a null container into the bitmap.

@Dr-Emann Dr-Emann requested a review from SLieve January 13, 2024 21:14
@Dr-Emann Dr-Emann changed the title container_remove_range returns null rather than returning an empty container roaring64: container_remove_range returns null rather than returning an empty container Jan 13, 2024
Copy link
Contributor

@SLieve SLieve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for finding it and for the fix! I saw in RoaringBitmap/croaring-rs#125 that you found most of these bugs with fuzzing, that's really cool :)

@Dr-Emann
Copy link
Member Author

The CI failure seems like it shouldn't be caused by my change, going to rebase to rerun the CI.

…ntainer

This could lead to an assert in `container_nonzero_cardinality`: typecode2 was
never set, so it was unlikely to be one of the known typecodes
@Dr-Emann Dr-Emann merged commit e861d74 into master Jan 14, 2024
44 checks passed
@Dr-Emann Dr-Emann deleted the push-rylnkxznopku branch January 14, 2024 17:33
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.

None yet

2 participants