-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Bug] Afar not working with cudf/dask-cudf/gpu-numba #29
Comments
Oh no! Thanks for the excellent bug report (and for using Perhaps |
That might work. Another option would be to spoof |
Release version 0.6.1 with the easy fix 🤞 . On PyPI, and should be available from conda-forge soon. Heh, I don't know whether to be proud or embarrassed by |
@eriknw awesome, we'll give it a try soon and I'll keep you updated! Edit: tried it and indeed it worked! Thank you for your work! |
When trying to use afar with
cudf
, it's not working the problem seems to be withnumba
when using gpu (numba jit by itself has no problems)Minimal reproducible example:
x.result()
retrievesafter looking into the traceback
I get the following:
I'm using
numba=0.53
which line 1157 corresponds to the following https://github.com/numba/numba/blob/release0.53/numba/core/typing/templates.py#L1157-L1159Which is trying to get
.__name__
fromLocalPrint
Looking at this all issue numpy/numpy#3112 (comment) it seems that in the
numba
end (https://github.com/numba/numba/blob/97fe221b3704bd17567b57ea47f4fc6604476cf9/numba/core/typing/templates.py#L1161-L1163) they are not updating the wraper as suggested here https://docs.python.org/3.3/library/functools.html#functools.update_wrapper, meaning that it is not assigning__name__
toLocalPrint
when it gets there.I wonder if there is a way of fixing this on
afar
maybe onLocalPrint()
.The text was updated successfully, but these errors were encountered: