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

fix(elementAt): force unsubscribe when it completes or errors #2501

Merged
merged 1 commit into from
Jun 14, 2017
Merged

fix(elementAt): force unsubscribe when it completes or errors #2501

merged 1 commit into from
Jun 14, 2017

Conversation

mpodlasin
Copy link
Contributor

Description:

Force unsubscription logic in elementAt, when resulting Observable completes or errors, so that all resources are disposed as fast as possible, even if next operator in chain does not unsubscribe reliably when given complete or error notification.

Related issue (if exists):
General issue is described here: #2459

Same fixes for other "take-like" operators: #2463 #2470

Force unsubscription logic in elementAt, when resulting Observable
completes or errors, so that all resources are disposed as fast
as possible, even if next operator in chain does not unsubscribe
reliably when given complete or error notification.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.001%) to 97.681% when pulling 49ecd6d on Podlas29:element-at-switch-map-fix into 3e9d529 on ReactiveX:master.

@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants