[Bug 725917] multiqueue: do not reset last push result when pushing events

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=725917
  GStreamer | gstreamer (core) | unspecified

Thiago Sousa Santos <thiago.sousa.santos> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.3.1

--- Comment #4 from Thiago Sousa Santos <thiago.sousa.santos at collabora.co.uk> 2014-03-10 16:12:05 UTC ---
commit 3ed2507ebc773ceb830012ae260949a52fe442a7
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Mon Mar 10 09:49:07 2014 -0300

    queue: queue2: preserve last flow result when pushing events

    Avoids mistakenly returning _OK when downstream is still
    _NOT_LINKED on subsequent received pad pushes

    https://bugzilla.gnome.org/show_bug.cgi?id=725917

commit b6470a7b3f26c203112db57b58afe8533b877963
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Mon Mar 10 09:48:58 2014 -0300

    multiqueue: do not reset last push result when pushing events

    Use the last result as a default when pushing a item from a single queue,
    otherwise the status gets reset to _OK when pushing events.

    This causes problems when mistakenly activating a not-linked stream
    that is being ignored upstream as it is not being used (adaptive
    scenarios), it will make the multiqueue post a buffering message
    on a pad that won't receive buffers

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.