Make the peek
method behaviour in the path selector deterministic #598
#600
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.
Description
Make a behaviour of the
peek
method of the path selector determenistic. To do it we fix taken random value betweenpoll
calls, so any sequence of thepeek
methods (and one followingpoll
call) will take the same element of the queue.Fixes #598
Type of Change
How Has This Been Tested?
Automated Testing
Any test for collections that try to find
NoSuchElementException
.Manual Scenario
You can set a debug point at any place where there are several elements in the path selector's queue, and call
peek
method multiple times. Check that it doesn't calculate a random value every time and returns the same value all the time.Checklist: