Update ResultSet.py #343
Merged
Update ResultSet.py #343
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes a bug where the tuple (src_id, dst_id, rank, edge_name) is used as the a key when accessing edges_dict, instead of the string representation of the tuple.
|
|
|
Dear @sherif-abdelkarim , Great catch, and thanks! Welcome to the NebulaGraph Community! Would you mind signing the CLA(by clicking above CLA badge) then we could merge your contributions then :D |
wey-gu
approved these changes
May 9, 2024
|
Hello @wey-gu , |
wey-gu
pushed a commit
that referenced
this pull request
Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a bug where the tuple (src_id, dst_id, rank, edge_name) is used as the a key when accessing edges_dict, instead of the string representation of the tuple.
What type of PR is this?
What problem(s) does this PR solve?
Issue(s) number:
Description:
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc: