-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Update arrow to include https://github.com/apache/arrow/pull/3392 #3765
Conversation
Test FAILed. |
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 change. I left one comment.
@@ -25,7 +25,7 @@ set(arrow_URL https://github.com/ray-project/arrow.git) | |||
# WARNING: If the arrow version is updated, you need to also update the | |||
# SETUPTOOLS_SCM_PRETEND_VERSION version string in the ThirdpartyToolchain.cmake | |||
# file | |||
set(arrow_TAG c347cd571e51723fc8512922f1b3a8e45e45b169) | |||
set(arrow_TAG f8c990e4165012123e03d822c95526eaea5cbfab) |
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.
Line 23 with # https://github.com/ray-project/arrow/commit/c347cd571e51723fc8512922f1b3a8e45e45b169
should also be changed, right? Is there a time line to merge apache/arrow#3177 , current status seems very inconvenient.
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.
Ok, I changed the link to the patch (originally I didn't because it's the same changes, but could be confusing I agree).
As for an upstream fix, I don't think it will happen any time soon. Also pytorch/tensorflow won't be fixed any time soon, see the discussion (they essentially can't do it on their own I think). It's really annoying, but there is not much we can do about it. The arguments from all sides make a lot of sense to me, probably what actually needs to happen is people need either to switch away from pip to conda, or nvidia needs to make sure that cuda is compatible with manylinux1 (or manylinux2010 in the future) to really fix this for everybody (I assume you followed the discussion in that issue and the mailing list).
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.
Understood.
Test FAILed. |
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.
LGTM. I will merge it once the CI passes.
Test PASSed. |
This is needed for #3734