Skip to content

fix(bufferTime): handle closing context when synchronously unsubscribed#1764

Merged
kwonoj merged 1 commit intoReactiveX:masterfrom
kwonoj:fix-buffertime
Jun 21, 2016
Merged

fix(bufferTime): handle closing context when synchronously unsubscribed#1764
kwonoj merged 1 commit intoReactiveX:masterfrom
kwonoj:fix-buffertime

Conversation

@kwonoj
Copy link
Member

@kwonoj kwonoj commented Jun 12, 2016

Description:
This PR updates behaviors of openContext and closeContext, do not try to update if contexts are cleared by synchronous unsubscription right after emitting value (i.e, take).

Related issue (if exists):

closes #1763

@coveralls
Copy link

Coverage Status

Coverage increased (+0.001%) to 96.348% when pulling 4ce4433 on kwonoj:fix-buffertime into 0a6c4e8 on ReactiveX:master.

@kwonoj
Copy link
Member Author

kwonoj commented Jun 18, 2016

I think change's ok, will check in around on this Sunday to next Monday if there isn't any suggestions.

@kwonoj kwonoj merged commit 8e727cd into ReactiveX:master Jun 21, 2016
@kwonoj kwonoj deleted the fix-buffertime branch June 21, 2016 05:32
@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.

Error on complete when using .bufferTime().take()

2 participants