This repository has been archived by the owner on Dec 26, 2022. It is now read-only.
Fix bug where graph-merger updates have equal forward_edge_name/reverse edge_name. #2100
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.
Which issue does this PR correspond to?
none. discovered today
What changes does this PR make to Grapl? Why?
I noticed in analyzer logging that the Updates we were getting had the same value for forward/reverse. That's wrong!
The easiest way to get the reverse edge name is to forward it from graph-mutation, which already does that lookup (and caches it).
How were these changes tested?
Added an integration test!