-
Notifications
You must be signed in to change notification settings - Fork 915
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
Another fix for offsets_end() iterator in lists_column_view #7575
Conversation
…st fix was still not correct---that iterator should not be computed using the size of the offsets() child column, which is also the offsets of the original (non-sliced) column
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.
Ah, my bad for suggesting you change it originally. That's a subtle issue I didn't consider!
You may want to run |
Hah, this is great. I just ran Probably it is a good practice to always call |
@gpucibot merge |
Codecov Report
@@ Coverage Diff @@
## branch-0.19 #7575 +/- ##
===============================================
+ Coverage 81.86% 82.40% +0.53%
===============================================
Files 101 101
Lines 16884 17342 +458
===============================================
+ Hits 13822 14290 +468
+ Misses 3062 3052 -10
Continue to review full report at Codecov.
|
…#7575) This is another fix for `offsets_end()` iterator in lists_column_view. The last fix (rapidsai#7551) was still not correct---that iterator should not be computed using the size of the `offsets()` child column, which is also the offsets of the original (non-sliced) column. Instead, it should be computed using the `size()` of the current column. Interestingly, my previous fix passed all the unit tests, since thrust does not throw anything (like access violation) when the input range is larger than the output range. Authors: - Nghia Truong (@ttnghia) Approvers: - Jake Hemstad (@jrhemstad) - David (@davidwendt) URL: rapidsai#7575
This is another fix for
offsets_end()
iterator in lists_column_view. The last fix (#7551) was still not correct---that iterator should not be computed using the size of theoffsets()
child column, which is also the offsets of the original (non-sliced) column. Instead, it should be computed using thesize()
of the current column.Interestingly, my previous fix passed all the unit tests, since thrust does not throw anything (like access violation) when the input range is larger than the output range.