Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoiding OperatorObserveOn from calling subscriber.onNext(..) after unsu... #1409

Merged
merged 1 commit into from
Jul 7, 2014

Commits on Jul 7, 2014

  1. Avoiding OperatorObserveOn from calling subscriber.onNext(..) after u…

    …nsubscribe().
    
    The OperatorObserveOn operator uses a scheduler to cancel subscriptions as well
    as to deliver the objects passing through it's onNext(..) in the right context.
    
    Calling unsubscribe will schedule the actual unsubscription while not making sure
    that the child subscriber will no longer receive calls to onNext(..) after
    unsubscribe() returns.
    
    This fix makes sure that after unsubscribe() returns no more onNext(..) calls will be
    made on the child subscribers.
    
    Signed-off-by: David Marques <dpsmarques@gmail.com>
    dpsm committed Jul 7, 2014
    Configuration menu
    Copy the full SHA
    cd4f112 View commit details
    Browse the repository at this point in the history