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
To fix this issue, datasets should return a copy of the global edgelist so the edgelist can be used in multiple places without affecting the original object.
The text was updated successfully, but these errors were encountered:
BradReesWork
changed the title
[BUG] Edgelist Returned from dataset.get_edgelist() is global
Edgelist Returned from dataset.get_edgelist() is global
Aug 3, 2023
We can also address this with documentation stating that a reference is being returned and that the caller should make a copy if needed. This makes it more of a documentation bug.
…ad of global (#3777)
Closes#3421
This PR fixes a bug where `get_edgelist()` would return a global edge list, which causes any changes made to the first returned edge list to be reflected in subsequent calls to `get_edgelist()`.
Now, `get_edgelist()` returns a copy of the dataframe stored by the `Dataset` object.
Authors:
- ralph (https://github.com/nv-rliu)
Approvers:
- Alex Barghi (https://github.com/alexbarghi-nv)
URL: #3777
Currently, when calling
get_edgelist()
, a global edgelist is returned. This causes issues when performing operations such as:Expected:
Actual:
To fix this issue, datasets should return a copy of the global edgelist so the edgelist can be used in multiple places without affecting the original object.
The text was updated successfully, but these errors were encountered: