Fix max-stop limit in StreetNearbyStopFinder #6160
Merged
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.
Summary
This PR fixes an issue in the StreetNearbyStopFinder with the max-stops counting.
The issue is that we use a SkipEdgeStrategy to keep track of how many stops we've passed. But a skip-edge strategy will be called once per edge, not once per vertex. This means that if a stop has
n
incoming edges it will be countedn
times and thus we might terminate the search before we've reached the desired number of stops.The documentation in SearchTerminationStrategy clearly says that it should be used for these kinds of purposes.
Unit tests
StreetNearbyStopFinderTest
since they will now pass.MaxCountTerminationStrategy
.Bumping the serialization version id
No