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

Take/Redo Unsubscribe #1793

Merged

Conversation

benjchristensen
Copy link
Member

Do not do further work after unsubscribed.

I added a fix to take on top of the change by @alexwen that fixes the source of the issue with take. It now unsubscribes before onNext so side-effects of onNext such as request(n) happen after unsubscribe and thus no further work will be scheduled.

I left the changes to OnSubscribeRedo as they are a good safety net in case another operator has a similar issue as take (an easy bug to creep in) as it does no harm to redo to have the isUnsubscribed check going forward.

Fixes #1791.

Alex Wenckus and others added 2 commits October 23, 2014 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant