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

timer doesn't work properly for large intervals #5155

Closed
bengry opened this issue Nov 20, 2019 · 1 comment
Closed

timer doesn't work properly for large intervals #5155

bengry opened this issue Nov 20, 2019 · 1 comment

Comments

@bengry
Copy link

bengry commented Nov 20, 2019

Bug Report

Current Behavior
If you start a timer with a time longer then 24 days, it emits all values immediattely. Using any time for up to 24 days (or even some fraction between 24 and 25 days, it breaks somewhere in the middle).

Reproduction

import { timer } from "rxjs";
import { tap, take } from "rxjs/operators";
import ms from "ms";

timer(0, ms("25 days")) // if you change this to 24, it works fine (supposedly, I didn't wait 24 days to see the next emittion, but it doesn't do it immediattely)
  .pipe(
    tap(e => {
      console.log("tap", e, new Date());
    }),
  )
  .subscribe();

Expected behavior
A clear and concise description of what you expected to happen (or code).

Environment

  • Runtime: Chrome v78
  • RxJS version: 6.5.3, also tried with 6.3.3, 6.0.0 and even 7.0.0-alpha.0
@kwonoj
Copy link
Member

kwonoj commented Nov 20, 2019

Dupe of #3015

@kwonoj kwonoj closed this as completed Nov 20, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants