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

Fix for issue 1406 #1502

Merged
merged 2 commits into from
Jun 13, 2022
Merged

Fix for issue 1406 #1502

merged 2 commits into from
Jun 13, 2022

Conversation

ioanaif
Copy link
Collaborator

@ioanaif ioanaif commented Jun 13, 2022

@ioanaif ioanaif requested a review from jpivarski June 13, 2022 17:48
Copy link
Member

@jpivarski jpivarski left a comment

Choose a reason for hiding this comment

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

This is totally correct: I verified that these are the tests @agoose77 mentions, and I would expect [[[], [2]]] sliced by [[[], [0]]] to return [[[], [2]]].

With a different layout (none of the IndexedOptionArrays, etc. that cause the bug), we do get this result:

>>> ak.Array([[[], [2]]])[ak.Array([[[], [0]]])]
<Array [[[], [2]]] type='1 * var * var * int64'>

So I'll merge it. Thanks!

@jpivarski jpivarski enabled auto-merge (squash) June 13, 2022 18:06
@codecov
Copy link

codecov bot commented Jun 13, 2022

Codecov Report

Merging #1502 (ce4af80) into main (5a78305) will not change coverage.
The diff coverage is n/a.

@jpivarski jpivarski merged commit 1adbf17 into main Jun 13, 2022
@jpivarski jpivarski deleted the ioanaif/fix-issue-1406 branch June 13, 2022 18:22
@agoose77
Copy link
Collaborator

Huh, nice find @ioanaif! It's painful how small a change this was!

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.

ListArray._getitem_next_jagged fails for slicecontent where starts[0] != 0 (v1 & v2)
3 participants