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
Hi,
I'm new to RxJava, please forgive me if this question feels too trivial. I'm currently learning by playing (in Scala), and I was surprised by the observation that
never terminates. After reading the description of zip, I was under the impression that it should complete after (the the shorter one) of the two sequences completes, which in this case is the abc, the interval is infinite. I'd expect the zip to unsubscribe from the collections that have not terminated yet after the first one completes, but it seems not to behave like that.
Is the current behavior intentional?
Thank you,
Tomáš Dvořák
The text was updated successfully, but these errors were encountered:
The current behavior is not what it should be. I've already reported an issue for this: #387 but no one has fixed it yet. Pull requests are welcome ;-)
The fix is not trivial, I spent some time on it last week and fixing this case is simple but it breaks other use cases. In practice I think the operator needs to be re-implemented from scratch instead of just tweaked for this case.
…andled co… (ReactiveX#484)
* Issue ReactiveX#480: Fixed a bug that CompletiongStage<Void> wasn't handled correctly in CircuitBreaker and Retry as the result was always null.
Hi,
I'm new to RxJava, please forgive me if this question feels too trivial. I'm currently learning by playing (in Scala), and I was surprised by the observation that
never terminates. After reading the description of zip, I was under the impression that it should complete after (the the shorter one) of the two sequences completes, which in this case is the abc, the interval is infinite. I'd expect the zip to unsubscribe from the collections that have not terminated yet after the first one completes, but it seems not to behave like that.
Is the current behavior intentional?
Thank you,
Tomáš Dvořák
The text was updated successfully, but these errors were encountered: