You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Python][GPU] numba-cuda dependency is maintenance mode only #51204
The numba-cuda project added a maintenance notice:
Numba-CUDA is in maintenance mode. Moving forward, we intend to support only security issues and critical bug fixes through the lifetime of CUDA 13. New feature development is targeted towards Numba-CUDA-MLIR, and we recommend upgrading to Numba-CUDA-MLIR as soon as practical. For migration guidance, see Migration from Numba / Numba-CUDA.
We should probably deprecate our usage of numba-cuda and migrate to numba-cuda-mlir. Not an expert on this area but using a deprecated maintenance only dependency doesn't sound great.
The error it used to raise (and that I still get locally) is Cuda error 1 in function 'cuMemcpyDtoH': [CUDA_ERROR_INVALID_VALUE] invalid argument. But the code is really trying to access an invalid pointer.
Activity
pitrou commentedon Sep 7, 2026
It's not really a dependency, though, its a third-party lib that we provide integration with :-)
So we can also provide an integration with the new thing if some contributor is interested.
@kkraus14 @leofang @tpn
raulcd commentedon Sep 7, 2026
Fair enough, should we remove the current third-party integration code? The CI jobs have been failing for months at this point.
pitrou commentedon Sep 7, 2026
Perhaps NVidia can task someone to fix CI? The failing builds that needs to be fixed AFAIK is https://github.com/apache/arrow/actions/runs/34091957769/job/101647306765
Ping @kkraus14 @leofang Again :-)
pitrou commentedon Sep 7, 2026
@raulcd Note that the crashing code on the CUDA Python CI is not Numba-related.
(and it's inherently crashy, though it used to raise an error before for some reason: I think we could simply remove it)
arrow/python/pyarrow/tests/test_cuda.py
Lines 300 to 306 in e235bdd
pitrou commentedon Sep 7, 2026
The error it used to raise (and that I still get locally) is
Cuda error 1 in function 'cuMemcpyDtoH': [CUDA_ERROR_INVALID_VALUE] invalid argument. But the code is really trying to access an invalid pointer.raulcd commentedon Sep 7, 2026
It originally started failing with:
pitrou commentedon Sep 7, 2026
We're talking about different failing tests here :)
leofang commentedon Sep 8, 2026
Q: Isn't this fix already merged? #51206
pitrou commentedon Sep 8, 2026
@leofang Right, sorry, that was a subthread but this issue is still valid.
leofang commentedon Sep 8, 2026
Got it. Now that the CI is fixed, is there anything else you need help with?
pitrou commentedon Sep 8, 2026
#49437 is not fixed (there's an attached PR that deserves reviewing and perhaps helping along).
leofang commentedon Sep 8, 2026
Seems like it'd be fixed by #50923. CUDA 11 support has been dropped since numba-cuda v0.19.0 (released in Aug, 2025).