Fix table result when source and destination on same one-way segment #5828
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.
Issue
Fixes #5788
Table queries where source and destination are phantom nodes on the same one-way segment can fail to find valid routes.
This is due to a bug in the MLD table generation for the special case where the query can be simplified to a
one-to-many search. If the destination is before the source on the one-way segment, it will fail to find a route.
We fix this case by not marking the node as visited at the start, so that valid paths to this node can be found later in the search.
We also remove redundant initialization for the source node as the same actions are performed by a search step.
Tasklist