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.
Problem Description
In the original pathfinding algorithm, a potential error in the recursive return causes paths at a certain depth (length) to be returned repeatedly. This leads to inconsistent probabilities when sampling paths because some paths are considered multiple times.
Example to Explain the Problem
Let’s consider a simple acyclic directed graph where we want to find all paths of a specific length(depth) starting from the specified node.
(Illustration is in .svg vector image format)
Now we implement the new function
find_paths()
to compare with the legancyget_reachable_from()
Then let's have some tests:
Result: ⬇️
We can find that the old one tells ['b', 'c', 'd'] and ['b', 'e', 'f'] twice respectively.
Result: ⬇️
It is obvious that the path ['a', 'b', 'c', 'd'], ['a', 'b', 'e', 'f'] are replicated in
get_reachable_from()
.As a result, we made the corresponding bug fix pull request.