Zip Bug UnitTest: Never Completes When Zero Observables (Obsolete) #868
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
RxJava-pull-requests #795 FAILURE |
|
That failure is expected, my test currently fails to prove the issue. |
|
RxJava-pull-requests #796 FAILURE |
|
Yup, that's a bug. The The line in question is here: https://github.com/Netflix/RxJava/blob/master/rxjava-core/src/main/java/rx/operators/OperatorZip.java?source=c#L110 |
Closed
|
RxJava-pull-requests #855 SUCCESS |
benjchristensen
added a commit
to benjchristensen/RxJava
that referenced
this pull request
Feb 21, 2014
Fixes bug reported at ReactiveX#868
benjchristensen
added a commit
to benjchristensen/RxJava
that referenced
this pull request
Feb 21, 2014
Fixes bug reported at ReactiveX#868
jihoonson
pushed a commit
to jihoonson/RxJava
that referenced
this pull request
Mar 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey guys,
I discovered this issue today in Rx. I'm not sure if it's a bug, or as designed. I've added the test. Can you let me know if it is in fact a bug, then I'll correct the issue?