-
Notifications
You must be signed in to change notification settings - Fork 3.7k
GH-40153: [Python] Fix OverflowError in foreign_buffer on 32-bit platforms #40158
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
Conversation
…t platforms Use `uintptr_t` rather than `intptr_t` to fix `OverflowError`, visible e.g. when running `tests/interchange/test_conversion.py` tests on 32-bit platforms.
|
Note that this doesn't address all issues from #40153, I've started with the one that seemed to have the biggest impact. |
@github-actions crossbow submit -g python -g wheel |
|
@github-actions crossbow submit -g python -g wheel |
Revision: d70772f Submitted crossbow builds: ursacomputing/crossbow @ actions-9e876b1e47 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @mgorny . This LGTM, I'll just wait for CI to pass.
CI failures are expected. Will merge. |
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit 29d2b16. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…t platforms (apache#40158) Use `uintptr_t` rather than `intptr_t` to fix `OverflowError`, visible e.g. when running `tests/interchange/test_conversion.py` tests on 32-bit platforms. ### Rationale for this change This fixes the `OverflowError`s from apache#40153, and makes `pyarrow/tests/interchange/` all pass on 32-bit x86. ### What changes are included in this PR? - change the type used to store pointer from `intptr_t` to `uintptr_t` to provide coverage for pointers above `0x80000000`. ### Are these changes tested? These changes are covered by the tests in `pyarrow/tests/interchange`. ### Are there any user-facing changes? It fixes `OverflowError` that can be triggered by working with pandas data types, possibly more (though I'm not sure if this qualifies as a "crash"). * Closes: apache#40153 Authored-by: Michał Górny <mgorny@gentoo.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
…t platforms (apache#40158) Use `uintptr_t` rather than `intptr_t` to fix `OverflowError`, visible e.g. when running `tests/interchange/test_conversion.py` tests on 32-bit platforms. ### Rationale for this change This fixes the `OverflowError`s from apache#40153, and makes `pyarrow/tests/interchange/` all pass on 32-bit x86. ### What changes are included in this PR? - change the type used to store pointer from `intptr_t` to `uintptr_t` to provide coverage for pointers above `0x80000000`. ### Are these changes tested? These changes are covered by the tests in `pyarrow/tests/interchange`. ### Are there any user-facing changes? It fixes `OverflowError` that can be triggered by working with pandas data types, possibly more (though I'm not sure if this qualifies as a "crash"). * Closes: apache#40153 Authored-by: Michał Górny <mgorny@gentoo.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
Use
uintptr_t
rather thanintptr_t
to fixOverflowError
, visible e.g. when runningtests/interchange/test_conversion.py
tests on 32-bit platforms.Rationale for this change
This fixes the
OverflowError
s from #40153, and makespyarrow/tests/interchange/
all pass on 32-bit x86.What changes are included in this PR?
intptr_t
touintptr_t
to provide coverage for pointers above0x80000000
.Are these changes tested?
These changes are covered by the tests in
pyarrow/tests/interchange
.Are there any user-facing changes?
It fixes
OverflowError
that can be triggered by working with pandas data types, possibly more (though I'm not sure if this qualifies as a "crash").