Skip to content

Operation mergeDelayError(Observable<Observable<T>>) does not delay onError of parent observable #313

Closed

Description

@EmteZogaf

Shouldn't all onError calls including a possible onError call of the parent observable being delayed till all child observables have successfully finished emitting items or called onError themselves?

To get my desired behaviour I changed the code so now the onError method adds the error to the error queue and calls the onCompleted method which already does the propagation of received errors.

Activity

  1. benjchristensen commented on Dec 6, 2013

    @benjchristensen
    Member

    If this is still an issue can you provide a unit test?

  2. EmteZogaf commented on Feb 19, 2014

    @EmteZogaf
    ContributorAuthor

    I wrote a unit test. An Observable of asynchronous child Observables is calling onError after emitting the child Observables.

    I created 2 branches:

  3. benjchristensen commented on May 20, 2014

    @benjchristensen
    Member

    Under what circumstances can the parent emit an error? The use cases you provide seem contrived, as mergeDelayError is a static method and therefore there is not a parent Observable to emit an error.

    Observable.mergeDelayError(o1, o2, o3).subscribe()

    In that code there are 3 Observable instances being merged, but no parent to emit an error.

  4. benjchristensen commented on Jul 24, 2014

    @benjchristensen
    Member

    Reviewing this again ... the signature where this could be an issue is:

    public final static <T> Observable<T> mergeDelayError(Observable<? extends Observable<? extends T>> source)
  5. added this to the 1.0 milestone on Jul 24, 2014
  6. benjchristensen commented on Jul 24, 2014

    @benjchristensen
    Member

    Marking to be included in 1.0 work.

  7. EmteZogaf commented on Jul 24, 2014

    @EmteZogaf
    ContributorAuthor

    I'm sorry for this late reply. I haven't looked into this issue for a while as our project using RxJava is running without any problems. But I will try to update to the new version next month and use base RxJava only without any customizations we made to it back then. If this is still an issue I'll report here.

  8. benjchristensen commented on Sep 23, 2014

    @benjchristensen
    Member

    Marking as 1.x as this doesn't require a signature change so can be fixed without holding up 1.0

  9. modified the milestones: , 1.0 on Sep 23, 2014
  10. modified the milestones: 1.0.x, , 1.0 on Oct 10, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions