Always set RMM's strides in the header
#4039
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to PR ( rapidsai/rmm#477 )
Fixes this test failure ( rapidsai/ucx-py#575 (comment) )
As newer versions of RMM have
DeviceBuffer
settingstrides
in__cuda_array_interface__
toNone
(as they are C-contiguous) and some deserializers rely on this to be a non-None
value, make sure to just explicitly setstrides
to a non-None
value.