-
Notifications
You must be signed in to change notification settings - Fork 3k
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
delay
regression after update to v7
#6932
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: