[GitHub] incubator-gearpump issue #238: [GEARPUMP-350] Fix app clock not started

[codecov-io]

Github user codecov-io commented on the issue:

https://github.com/apache/incubator-gearpump/pull/238
  
# 
[Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/238?src=pr=h1)
 Report
> Merging 
[#238](https://codecov.io/gh/apache/incubator-gearpump/pull/238?src=pr=desc) 
into 
[master](https://codecov.io/gh/apache/incubator-gearpump/commit/69f9006143fedbb7a3619974c5c7d6946b0d002b?src=pr=desc)
 will **decrease** coverage by `0.17%`.
> The diff coverage is `100%`.



```diff
@@Coverage Diff @@
##   master #238  +/-   ##
==
- Coverage   69.35%   69.17%   -0.18% 
==
  Files 191  191  
  Lines6124 6124  
  Branches  539  539  
==
- Hits 4247 4236  -11 
- Misses   1877 1888  +11
```




---

[GitHub] incubator-gearpump pull request #238: [GEARPUMP-350] Fix app clock not start...

[manuzhang]

GitHub user manuzhang opened a pull request:

https://github.com/apache/incubator-gearpump/pull/238

[GEARPUMP-350] Fix app clock not started

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-] 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 https://github.com/manuzhang/incubator-gearpump 
fix_app_not_started

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

https://github.com/apache/incubator-gearpump/pull/238.patch

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

This closes #238


commit d0d4448015a899f2003b40181b80cfe341889370
Author: manuzhang 
Date:   2018-03-12T02:05:31Z

[GEARPUMP-350] Fix app clock not started




---

[jira] [Commented] (GEARPUMP-350) the app Clock is not started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394742#comment-16394742
 ] 

ASF GitHub Bot commented on GEARPUMP-350:
-

Github user codecov-io commented on the issue:

https://github.com/apache/incubator-gearpump/pull/238
  
# 
[Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/238?src=pr=h1)
 Report
> Merging 
[#238](https://codecov.io/gh/apache/incubator-gearpump/pull/238?src=pr=desc) 
into 
[master](https://codecov.io/gh/apache/incubator-gearpump/commit/69f9006143fedbb7a3619974c5c7d6946b0d002b?src=pr=desc)
 will **decrease** coverage by `0.17%`.
> The diff coverage is `100%`.



```diff
@@Coverage Diff @@
##   master #238  +/-   ##
==
- Coverage   69.35%   69.17%   -0.18% 
==
  Files 191  191  
  Lines6124 6124  
  Branches  539  539  
==
- Hits 4247 4236  -11 
- Misses   1877 1888  +11
```




> the app Clock is not started
> 
>
> Key: GEARPUMP-350
> URL: https://issues.apache.org/jira/browse/GEARPUMP-350
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Pan Xue
>Priority: Major
> Attachments: gearpump0.8.4.PNG
>
>
> When I submitted an app in the web,  in the DAG display page, I found that 
> the application clock has been not started, the source processor's color will 
> turn red, I use the example is 0.8.4 version of the example / wordcount
> !gearpump0.8.4.PNG|thumbnail!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEARPUMP-350) the app Clock is not started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEARPUMP-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394739#comment-16394739
 ] 

ASF GitHub Bot commented on GEARPUMP-350:
-

GitHub user manuzhang opened a pull request:

https://github.com/apache/incubator-gearpump/pull/238

[GEARPUMP-350] Fix app clock not started

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-] 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 https://github.com/manuzhang/incubator-gearpump 
fix_app_not_started

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

https://github.com/apache/incubator-gearpump/pull/238.patch

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

This closes #238


commit d0d4448015a899f2003b40181b80cfe341889370
Author: manuzhang 
Date:   2018-03-12T02:05:31Z

[GEARPUMP-350] Fix app clock not started




> the app Clock is not started
> 
>
> Key: GEARPUMP-350
> URL: https://issues.apache.org/jira/browse/GEARPUMP-350
> Project: Apache Gearpump
>  Issue Type: Bug
>Affects Versions: 0.8.4
>Reporter: Pan Xue
>Priority: Major
> Attachments: gearpump0.8.4.PNG
>
>
> When I submitted an app in the web,  in the DAG display page, I found that 
> the application clock has been not started, the source processor's color will 
> turn red, I use the example is 0.8.4 version of the example / wordcount
> !gearpump0.8.4.PNG|thumbnail!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Podling Report Reminder - March 2018

[John D . Ament]

All,

Please see below reminder.  No report has been filed, is one expected?  It 
seems like activity may have died out.

John

On 2018/03/07 01:32:29, johndam...@apache.org wrote: 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 21 March 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, March 07).
> 
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://wiki.apache.org/incubator/March2018
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
> 
> Incubator PMC
>