-
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
Error with race
and sync Observables
#1615
Comments
I don't think this is expected behavior, Observable should not throw in this case. Let me try look into to see what's happening. |
kwonoj
added a commit
to kwonoj/rxjs
that referenced
this issue
Apr 14, 2016
I was mildly excited when I thought @matthewwithanm was "Matthew with ham". Then I reread it. Can't win 'em all. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
RxJS version:
5.0.0-beta.6
Code to reproduce:
At the Node (v5.0.0) console:
Expected behavior:
Actual behavior:
Additional information:
If I
delay
both, I don't get the TypeError. If I usetoPromise
and then.then
it, rather than callingsubscribe
I don't get the TypeError.It seems clear that it's a result of one of the Observables being synchronous. However if this is expected behavior I have two questions: (1) What should I do instead, if I receive Observables that may or may not be sync? (2) Why does the error appear to be an internal error, rather than a user-facing error?
cc @matthewwithanm
The text was updated successfully, but these errors were encountered: