Skip to content

2.x: Fix Flowable + Single elementAt and elementAtOrError operators on empty sources#4681

Merged
akarnokd merged 1 commit intoReactiveX:2.xfrom
vanniktech:elemen_at
Oct 7, 2016
Merged

2.x: Fix Flowable + Single elementAt and elementAtOrError operators on empty sources#4681
akarnokd merged 1 commit intoReactiveX:2.xfrom
vanniktech:elemen_at

Conversation

@vanniktech
Copy link
Collaborator

This will fix #4680

  • elementAtOrError(1) on an empty source just leaves the new Single hanging without signalling onError()
  • elementAt(1) on an empty source just leaves the Maybe hanging without signalling onComplete()
  • I also noticed that elementAt() with a default value on an empty source did not work either.

@akarnokd akarnokd added the Bug label Oct 7, 2016
@akarnokd akarnokd added this to the 2.0 RC5 milestone Oct 7, 2016
@codecov-io
Copy link

codecov-io commented Oct 7, 2016

Current coverage is 82.15% (diff: 0.00%)

Merging #4681 into 2.x will increase coverage by 0.17%

@@                2.x      #4681   diff @@
==========================================
  Files           565        565          
  Lines         37426      37426          
  Methods           0          0          
  Messages          0          0          
  Branches       5746       5746          
==========================================
+ Hits          30682      30749    +67   
+ Misses         4666       4608    -58   
+ Partials       2078       2069     -9   

Powered by Codecov. Last update 27e8dad...5e3ce8e

@akarnokd
Copy link
Member

akarnokd commented Oct 7, 2016

You may have to check the build and restart it a few times if it fails with jacocoTestReport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2.x: ElementAt Operators in Observable and Flowable don't behave correctly on empty sources

3 participants