fix(stackPrefetch): Cleans up stack prefetching order logic #1132
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix / cleanup
What is the current behavior? (You can also link to an open issue here)
Changes in #1074 accidentally reversed the stack prefetching queue of imageIds returned from the prioritization algorithm. This was later fixed in #1089 here by passing the
addToBeginning
flag to therequestPoolManager
. This PR removes the array reversal which removes the need for the flag as well.I noticed this issue because I was still running on v4.2.0, the
addToBeginning
flag fixes things in more recent versions but I thought it was worth cleaning up!What is the new behavior (if this is a feature change)?
N/A
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
N/A
Other information: