UnicastContentSubject unsubscribes eagerly #341
Merged
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.
UnicastContentSubjectdelegates buffering to aBufferUntilSubscribersubject. However, it subscribes the downstream subscriber to this subject usingObservable.unsubscribe(). This causes aSafeSubscribersubscribing to the buffer subject which unsubscribes on termination of the upstream source.The following code reproduces the issue:
In the above code the flatmap returns
Observable.never()which should not get unsubscribed, unless the eventual subscriber unsubscribes.Using
unsafeSubscribe()to subscribe to theBufferUntilSubscriberwill not eagerly unsubscribe.