Fix newer numpy integer out of bounds issues in ImageNet dataset#337
Fix newer numpy integer out of bounds issues in ImageNet dataset#337LVeefkind wants to merge 1 commit into
Conversation
|
Hi @LVeefkind! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
For NumPy>=2.0
np.uint32(-1)results in an OverFlowError as -1 is out of bounds for uint32. Older NumPy versions would silently wrap it to4294967295(the maximum of uint32). This new line should fix it while achieving the same result