We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I thought subsequent calls to o.error would be noop but that does not seem to be case. Consider the following sample:
o.error
require('rxjs-compat') const { Observable } = require('rxjs') Observable .create((o) => { console.log('create') setTimeout(() => o.error(1), 100) setTimeout(() => o.error(2), 200) }) .retryWhen((err$) => err$ .do((err) => { console.log('error', err) }) .delay(1e3) ) .subscribe()
Running this will cause a lot of parallel retries to start.
create error 1 error 2 create create error 1 error 1 error 2 error 2 create create create error 1 create error 1 error 1 error 2 error 1 error 2 error 2 error 2
Is this a bug or intentional?
The text was updated successfully, but these errors were encountered:
It's a bug: #5115
Closing this in favour of the linked issue.
Sorry, something went wrong.
No branches or pull requests
I thought subsequent calls to
o.error
would be noop but that does not seem to be case. Consider the following sample:Running this will cause a lot of parallel retries to start.
Is this a bug or intentional?
The text was updated successfully, but these errors were encountered: