You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
import{timer}from"rxjs";import{tap,take}from"rxjs/operators";importmsfrom"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,newDate());}),).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
The text was updated successfully, but these errors were encountered:
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
take(100)
here just to limit the amount of output).Expected behavior
A clear and concise description of what you expected to happen (or code).
Environment
6.5.3
, also tried with6.3.3
,6.0.0
and even7.0.0-alpha.0
The text was updated successfully, but these errors were encountered: