-
Notifications
You must be signed in to change notification settings - Fork 73
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
Fix pinning to a different RAFT tag #235
Conversation
Attempting to pin the version of a raft to a custom fork wasn't working, and it was still using the version installed by conda. Fix by mirroing the `CUML_RAFT_CLONE_ON_PIN` logic found in the cuml cmake files.
python/cuvs/CMakeLists.txt
Outdated
@@ -37,6 +37,7 @@ project( | |||
option(FIND_CUVS_CPP "Search for existing CUVS C++ installations before defaulting to local files" | |||
OFF | |||
) | |||
set(CUVS_RAFT_CLONE_ON_PIN OFF) |
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.
Why does this need to be set off?
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.
I copied the logic here from cuml https://github.com/rapidsai/cuml/blob/99b20f67c6dea4aba80da5787f64557dba30a1f8/python/cuml/CMakeLists.txt#L41 - but now I'm wondering if this might have been accidentally applied in cuml in rapidsai/cuml#4990 , and not meant to be included there permanently.
Removed in latest commit
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 tracking that down, definitely looks to be accidental.
/merge |
Attempting to pin the version of a raft to a custom fork wasn't working, and it was still using the version installed by conda. Fix by mirroing the
CUML_RAFT_CLONE_ON_PIN
logic found in the cuml cmake files.