Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
Description
While reviewing some code I realized that there is no bounds checking on ArrowBuf slicing. Example negative test case that should pass but is currently failing can be found here:
https://gist.github.com/jacques-n/737c26b7016ed29dc710d4aba617340e
It may be that this doesn't cause more problems because the index checks do exist on memory access but fixing this would make it much easier to understand where a code mistake was made.
Attachments
Issue Links
- links to