2.x: Fix the error/race in Observable.repeatWhen due to flooding repeat signal #6359
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.
This PR fixes a race condition in the
ObservableRepeatWhen
operator for the case when the repeat signal is not 1-for-1 and a new subscription may race with the clearing of the previous disposable becauseactive
is set tofalse
too early. The fix is to swap the two operations.Observable.retryWhen
and theFlowable
versions do not have this bug. Unit tests were added to all 4 operators to verify the correct behavior regardless.Fixes: #6358