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(scheduler): prevent unwanted clearInterval #3226

Merged
merged 2 commits into from
Jan 16, 2018

Conversation

cartant
Copy link
Collaborator

@cartant cartant commented Jan 13, 2018

Description:

Reinstates the commits that were made in #3044 and reverted in #3152.

The problem that effected the reversion was not caused by PR #3044. See the related issue (#3225) for details.

Related issue (if exists): #3225 #3044

In AsyncAction, this.pending was assigned before the call to
recycleAsyncId. That prevented the interval from being re-used resulting
in the interval being cleared and re-created for each notification.

Closes ReactiveX#3042
@rxjs-bot
Copy link

Messages
📖

CJS: 1381.5KB, global: 750.2KB (gzipped: 120.6KB), min: 145.4KB (gzipped: 31.4KB)

Generated by 🚫 dangerJS

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 97.111% when pulling 53bdfe9 on cartant:issue-3225 into 1a363ad on ReactiveX:master.

@benlesh benlesh merged commit d7cfb42 into ReactiveX:master Jan 16, 2018
@benlesh
Copy link
Member

benlesh commented Jan 16, 2018

Thanks again, @cartant!

@lock
Copy link

lock bot commented Jun 5, 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 5, 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.

4 participants