-
Notifications
You must be signed in to change notification settings - Fork 301
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
[REVIEW] Bring up cugraph_dgl_repo #2896
[REVIEW] Bring up cugraph_dgl_repo #2896
Conversation
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.
👍
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## branch-22.12 #2896 +/- ##
===============================================
Coverage ? 60.81%
===============================================
Files ? 122
Lines ? 6891
Branches ? 0
===============================================
Hits ? 4191
Misses ? 2700
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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 didn't see any showstoppers, but I did have several questions and minor requests. I like that the test coverage seems good and that they are easy to follow.
|
||
|
||
Read the user guide chapter :ref:`guide-`CuGraphStorage` for an in-depth | ||
explanation about its usage. | ||
|
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.
minor: redundant blank lines
num_nodes_dict: dict, | ||
single_gpu: bool = True, | ||
cugraph_service_client=None, | ||
device_id=0, |
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.
Throughout this file too are cases of some args with type hints, some without. Should we be enforcing in reviews that these be present on new code, or would this be a FIXME type of situation for now?
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 have added all the type-hints that are possible without adding extra imports. The missing ones are now dgl objects
and dataframe
objects that depends on the underlying library (for dgl bakcend, it can be pytorch, tensorflow,keras) and for dataframe
can be (cuDF,dask_cuDF, pandas
).
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.
Have added issue: #2922 to track it.
Co-authored-by: Rick Ratzel <3039903+rlratzel@users.noreply.github.com>
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, thanks.
@gpucibot merge |
This PR resolves https://github.com/rapidsai/graph_dl/issues/92