-
Notifications
You must be signed in to change notification settings - Fork 1.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
Fix the issue that the query results will still contain the expired e… #3536
Conversation
…dges if we use go reversely
Codecov Report
@@ Coverage Diff @@
## master #3536 +/- ##
==========================================
+ Coverage 85.19% 85.21% +0.01%
==========================================
Files 1306 1307 +1
Lines 122158 122578 +420
==========================================
+ Hits 104078 104460 +382
- Misses 18080 18118 +38
Continue to review full report at Codecov.
|
…x_reverse_edge_ttl
@Sophie-Xie any comment? does it look OK? |
Thanks. I assign it to others, pls wait for their review. |
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
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.
Gooood job~ thx~ This bug must have existed for a long time
…dges if we use go reversely
What type of PR is this?
What does this PR do?
Fix an issue that the query results still contain the expired edges when use go reversely
Which issue(s)/PR(s) this PR relates to?
Special notes for your reviewer, ex. impact of this fix, etc:
Additional context/ Design document:
Checklist:
Release notes:
Please confirm whether to be reflected in release notes and how to describe: