Ensure that all raced promises are resolved after the race #151
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.
Each race spawns a new promise for every promise being raced, and long-lived promises can cause an issue with that.For each promise being raced, it's safe to resolve it immediately after the race if we can guarantee that no one else is waiting on it.There are 3 places of significance when it comes to racing:
#maxPollIntervalRestart
. Only other site is cacheExpirationLoop and these two methods are never called together, as one calls the other.cacheExpirationLoop
: this is racing both #maxPollIntervalRestart and #workerTerminationScheduled. The first one can be resolved safely with the same logic as (1). For #workerTerminationScheduled we can actually remove it from the race. Why? Because #workerTerminationScheduled resolved means that very soon #maxPollIntervalRestart will be resolved too (in the main runInternal loop). Otherwise the timer will expire but then the while loop will check the expiry of #workerTerminationScheduled .This addresses #150