gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEARPUMP-320) Stashed messages are not processed
Date Fri, 23 Jun 2017 01:32:01 GMT


ASF GitHub Bot commented on GEARPUMP-320:

GitHub user manuzhang opened a pull request:

    [GEARPUMP-320] Handle stashed messages after onStart

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the commit message is formatted like:
       `[GEARPUMP-<Jira issue #>] Meaningful description of pull request` 
     - [ ] Make sure tests pass via `sbt clean test`.
     - [ ] Make sure old documentation affected by the pull request has been updated and new
documentation added for new functionality. 

You can merge this pull request into a Git repository by running:

    $ git pull fix_start

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #192
commit d2aa227e8ee16476d97843fd6f6379767f87826f
Author: manuzhang <>
Date:   2017-06-23T01:30:13Z

    [GEARPUMP-320] Handle stashed messages after onStart


> Stashed messages are not processed 
> -----------------------------------
>                 Key: GEARPUMP-320
>                 URL:
>             Project: Apache Gearpump
>          Issue Type: Bug
>          Components: streaming
>    Affects Versions: 0.8.3
>            Reporter: Manu Zhang
>            Assignee: Manu Zhang
> This is because stashed messages are handled before _TaskActor.onStart_ creating _Task_.

This message was sent by Atlassian JIRA

View raw message