2.x: UnicastSubject fix for the child becoming visible before onSubscribe is called. #3381
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.
Discovered while the test
NbpOperatorConcatTest.testIssue2890NoStackoverflow
hung on Travis.What happened is that the reference to the child became visible before the call to its
onSubscribe
method so a concurrent source emitting at the exact same time could already see the "unstarted" child. The PR fixes this in bothNbpUnicastSubject
andUnicastSubject
by changing the order of calls. The rest of the subjects behave correctly (callonSubscribe
first, make child visible second).In addition,
UnicastSubject
now callsdrain()
because when theonSubscribe
callsrequest
anddrain
, the child is not visible and nothing gets replayed. Once bothonSubscribe
call returns and the child is becomes visible, a call todrain
again will now correctly replay all available contents that were requested.