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
Delay operator does not delay for the given time after some threshold. For shorter values like 12 hours, it works well.
Expected behavior
delay is the same as expected
Reproduction code
import{of}from"rxjs";import{delay,tap}from"rxjs/operators";letstart: number;of(null).pipe(tap(()=>{console.log("ASSIGNED");start=newDate().getTime();}),delay(63158404179),).subscribe(()=>console.log("DELAYED",newDate().getTime()-start));// result like DELAYED 965
Since rxjs uses native browser runtime's timer, the maximum allowed value was always same for any time related operator. see #3015 for dupe, which was having same beahavior since v5.
Not really, I have tested it on my previous 6.7 version and it did not finished "so fast". Of course, I did not wait 2 years, but it behaved in a different way. This is a regression.
Describe the bug
Delay operator does not delay for the given time after some threshold. For shorter values like 12 hours, it works well.
Expected behavior
delay is the same as expected
Reproduction code
Reproduction URL
No response
Version
7.5.5
Environment
Angular CLI: 13.3.2
Node: 16.14.2
Package Manager: npm 8.5.0
OS: win32 x64
Angular:
...
Package Version
@angular-devkit/architect 0.1303.2 (cli-only)
@angular-devkit/core 13.3.2 (cli-only)
@angular-devkit/schematics 13.3.2 (cli-only)
@schematics/angular 13.3.2 (cli-only)
Additional context
No response
The text was updated successfully, but these errors were encountered: