Closed masonproffitt closed 1 year ago
This issue might need to be on https://github.com/dask-contrib/dask-awkward. I think the fix is going to involve changes to that codebase, not this one.
Going by the stack-trace, we're raising a StopIteration
exception if the indexing shape is out-of-bounds in typetracer. We should be raising an IndexError
here, which would then be caught and re-thrown by
https://github.com/scikit-hep/awkward/blob/7fbe6b856cb87cfbe5a4827b7586852c49ff2bbe/src/awkward/contents/numpyarray.py#L346-L348
Oh, okay. So it is something to do here.
Description of new feature
Trying to slice an Awkward Array in too many dimensions raises a helpful error:
Whereas for
dask-awkward
arrays, you get this much less friendly uncaughtStopIteration
, coming fromtypetracer
:Ideally, this case should produce a message similar to the first example.