-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Fix issue #1451 #1454
Fix issue #1451 #1454
Conversation
RxJava-pull-requests #1403 SUCCESS |
RxJava-pull-requests #1404 SUCCESS |
RxJava-pull-requests #1405 SUCCESS |
@@ -70,7 +70,9 @@ public void request(long n) { | |||
} | |||
o.onNext(it.next()); | |||
} | |||
o.onCompleted(); | |||
if (!o.isUnsubscribed()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this considered such a problem? This is always possible to have happen from an Observable
and nothing should be sensitive to it happening since unsubscribe
can be a race condition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. Should I send a PR to remove it, or just keep it?
I don't think we should need to be checking |
Add
done
to make sure callingdoOnEachObserver
obey the Rx contract.