We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description A clear and concise description of the bug and the associated functionality.
various bugs when using index arrays for indexing on distributed one-dimensional DNDarrays.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen. Return DNDarray with indexed values.
Illustrative If applicable, add screenshots or minimal examples to help explain your problem.
x = ht.arange(10,1,-1, split=0) # wrong order on procs > 2 x[ht.array([3, 3, 1, 8])] # Segmentation fault procs > 1 x[ht.array([3,3,-3,8])] # Runtime error procs > 1 x[ht.array([[1,1],[2,3]])]
Version Info master f7f6c35
Additional comments Any other comments here. First case related to #703
Not tested yet:
The text was updated successfully, but these errors were encountered:
Branch bugs/824-indexing_vectors_with_index_arrays created!
Sorry, something went wrong.
Still open, addressed in #938
reviewed within #1109
ClaudiaComito
No branches or pull requests
Description
A clear and concise description of the bug and the associated functionality.
various bugs when using index arrays for indexing on distributed one-dimensional DNDarrays.
To Reproduce
Steps to reproduce the behavior:
getitem
array indexing on distributed 1d arrays
Runtime error / Segmentation fault
Expected behavior
A clear and concise description of what you expected to happen.
Return DNDarray with indexed values.
Illustrative
If applicable, add screenshots or minimal examples to help explain your problem.
Version Info
master f7f6c35
Additional comments
Any other comments here.
First case related to #703
Not tested yet:
The text was updated successfully, but these errors were encountered: