[jira] [Commented] (EAGLE-358) add help for 404 error on Eagle UI

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385221#comment-15385221
 ] 

ASF GitHub Bot commented on EAGLE-358:
--

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/253
  
@peterkim95 this PR has been merged to develop branch, you're now free to 
close it.


> add help for 404 error on Eagle UI
> --
>
> Key: EAGLE-358
> URL: https://issues.apache.org/jira/browse/EAGLE-358
> Project: Eagle
>  Issue Type: Improvement
> Environment: Horton Sandbox, Virtualbox
>Reporter: Peter Kim
>Priority: Minor
>  Labels: documentation, easyfix
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I've noticed that some people, including myself, were running into an 404 
> error when trying to access the Eagle UI after successfully finishing 
> examples/eagle-sandbox-starter.sh
> The README.md doesn't explain this but this can be fixed with a simple 
> addition of port 9099 to the virtualbox port forwarding rules (instruction #4 
> on https://eagle.incubator.apache.org/docs/quick-start.html)
> I felt like this should be included/referenced in the final README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #253: EAGLE-358 add help for 404 error on Eagle UI

[anyway1021]

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/253
  
@peterkim95 this PR has been merged to develop branch, you're now free to 
close it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request #267: Eagle 376 skip false failing hbase relate...

[anyway1021]

Github user anyway1021 closed the pull request at:

https://github.com/apache/incubator-eagle/pull/267


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-358) add help for 404 error on Eagle UI

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385180#comment-15385180
 ] 

ASF GitHub Bot commented on EAGLE-358:
--

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/253
  
The content looks good. According to our current branching convention, 
we'll merge it to "develop" branch. 

See branching convention at: 
https://cwiki.apache.org/confluence/display/EAG/Branching+Convention

Thanks.


> add help for 404 error on Eagle UI
> --
>
> Key: EAGLE-358
> URL: https://issues.apache.org/jira/browse/EAGLE-358
> Project: Eagle
>  Issue Type: Improvement
> Environment: Horton Sandbox, Virtualbox
>Reporter: Peter Kim
>Priority: Minor
>  Labels: documentation, easyfix
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I've noticed that some people, including myself, were running into an 404 
> error when trying to access the Eagle UI after successfully finishing 
> examples/eagle-sandbox-starter.sh
> The README.md doesn't explain this but this can be fixed with a simple 
> addition of port 9099 to the virtualbox port forwarding rules (instruction #4 
> on https://eagle.incubator.apache.org/docs/quick-start.html)
> I felt like this should be included/referenced in the final README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #253: EAGLE-358 add help for 404 error on Eagle UI

[anyway1021]

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/253
  
The content looks good. According to our current branching convention, 
we'll merge it to "develop" branch. 

See branching convention at: 
https://cwiki.apache.org/confluence/display/EAG/Branching+Convention

Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Web site branding

[Julian Hyde]

I’ve replied to the JIRA ticket. Let’s move the conversation there.

> On Jul 19, 2016, at 12:43 AM, Michael Wu  wrote:
> 
> @ Julian, or you may give your further comments on ticket EAGLE-380
> . Thanks.
> 
> On Tue, Jul 19, 2016 at 3:28 PM, Michael Wu  wrote:
> 
>> Hi Julian,
>> 
>> Could you take a look at the 1st (disclaimer more prominent) and 3rd
>> (remove forking flag) topic in the last sending, please? I may need your
>> confirmation to make it clear in my mind, thanks a lot!
>> 
>> Michael
>> 
>> On Mon, Jul 18, 2016 at 5:09 PM, Michael Wu  wrote:
>> 
>>> @Julian,
>>> 
>>> (copy my reply from another thread and paste it as below)
>>> 
>>> Just copy your comments here and adding my comments. Thank you for the
>>> suggestions.
>>> 
>>> [Julian] - Also, make the disclaimer more prominent on the front page. It
>>> is buried at the bottom of a very long page. I think it should appear in
>>> the first screen-full.
>>> [Michael] - a find an example from Apache Blur Incubating, do you mean
>>> something similar to its disclaimer appears on front page? Such as:
>>> http://incubator.apache.org/blur/.
>>> 
>>> [Julian] - In the docs, qualify all Apache projects with Apache. I think
>>> you can skip "Apache" in the tag line "Secure Hadoop in real time" but you
>>> must acknowledge trademarks.
>>> [Michael] -
>>> 1. in the new site doc, I have added "Apache" preceding first mention of
>>> "eagle" on every page, and commented the following "Eagle" on the page is
>>> pointing to "Apache Eagle (incubating)".
>>> 2. "acknowledge trademarks", do you mean the trademarks of "hadoop". If I
>>> understand right, the "tag line" you mentioned has been modified, it would
>>> never mention "Hadoop" again.
>>> 
>>> [Julian] - In the docs, remove "fork me on github" from the top right
>>> corner. The call to action is to join the Apache community.
>>> [Michael] - Not quite clear with this tip. I'm wondering, where is the
>>> appropriate position for us to place the "forking" element on the page? As
>>> least, people may contribute by firstly forking a git repository. Do you
>>> think the top-nav tag bar is good to add forking components?
>>> 
>>> 
>>> Thanks.
>>> Michael
>>> 
>>> On Mon, Jul 18, 2016 at 4:02 PM, Julian Hyde  wrote:
>>> 
 I added the following comments to the JIRA case:
 
 * Also, make the disclaimer more prominent on the front page. It is
 buried at the bottom of a very long page. I think it should appear in the
 first screen-full.
 
 * Apply these guidelines throughout the site, in particular to the docs,
 https://eagle.incubator.apache.org/docs/.
 
 * In the docs, qualify all Apache projects with Apache. I think you can
 skip "Apache" in the tag line "Secure Hadoop in real time" but you must
 acknowledge trademarks.
 
 * In the docs, remove "fork me on github" from the top right corner. The
 call to action is to join the Apache community.
 
 Julian
 
> On Jul 17, 2016, at 8:32 PM, Michael Wu  wrote:
> 
> BTW, here is a jira ticket for trying to fix this issue: EAGLE-380
> . It'll be thankful
 to see
> your comments on it. :)
> 
> On Mon, Jul 18, 2016 at 11:29 AM, Michael Wu 
 wrote:
> 
>> Hi guys,
>> 
>> To my understanding on your suggestions, we could modify our docs in
 the
>> following ways, please help review if they are satisfying the request:
>> 1. if "eagle" is in doc page title, change it to "Apache Eagle
>> (incubating)".
>> 2. if there are many "eagle"s appear in the doc page content, change
 the
>> first mention of it to "Apache Eagle (incubating, called Eagle in the
>> following)".
>> 3. change logo size or position.
>> 
>> Anything missed, please DO correct me. Thanks.
>> Michael
>> 
>> 
>> On Thu, Jun 30, 2016 at 11:05 PM, Henry Saputra <
 henry.sapu...@gmail.com>
>> wrote:
>> 
>>> Yeah, thinking moving the link and incubator logo up in the header
 and
>>> keep
>>> the incubator disclaimer as footer.
>>> 
>>> Also move some content in between to separate page to make visitor
 scroll
>>> less for homepage.
>>> 
>>> Thoughts?
>>> 
>>> - Henry
>>> 
>>> On Thu, Jun 30, 2016 at 6:31 PM, John D. Ament <
 johndam...@apache.org>
>>> wrote:
>>> 
 
 
 On 2016-06-29 20:48 (-0400), Henry Saputra  
 wrote:
> Probably we could move this section to Powered By Eagle page so
>>> homepage
> could be more clear it is part of ASF and also include Incubator
> description on top of page.
 
 So you're thinking about moving some of the ASF logos up, not
 buried in
 the footer?
 
> 
> On Thursday, June 30, 2016, arunkarthick m  
 wrot

[jira] [Commented] (EAGLE-380) fix eagle site/doc branding issue

[Julian Hyde (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384698#comment-15384698
 ] 

Julian Hyde commented on EAGLE-380:
---

1. Yes, something like blur. Or, since there is already the line "Eagle has 
been accepted as an Apache Incubator Project on Oct 26, 2015", the disclaimer 
could replace that line.

2a. Sounds good.

2b. Yes, if you use Hadoop you should add "Hadoop" to the list "Apache Eagle, 
Eagle, Apache, the Apache feather logo, and the Apache Incubator project logo 
are trademarks of The Apache Software Foundation". Maybe you no longer mention 
Hadoop. But currently you mention several Apache projects, including Storm, 
Spark, Ambari, Hive, so you should qualify them with "Apache" and add them to 
the list.

3. It's not appropriate for an Apache project to be saying "Fork me on Github". 
Sure, you want people to get the source code, but you also want them to know 
about mailing lists, JIRA etc.

Let's suppose I want to know how to get started as a developer. I'd probably 
click on "Community" then click "How to contribute", which takes me to... 
https://github.com/eBay/Eagle/wiki/How-to-Contribute. Oops, let's fix that!

Or, if I was starting at https://eagle.incubator.apache.org/docs/ I'd click 
"Development Quick Guide". Put a paragraph there, showing them how to "git 
clone ...; mvn install ...".

The information in 
https://github.com/apache/incubator-eagle/blob/master/README.md is great; maybe 
it should be in the Development Quick Guide.

> fix eagle site/doc branding issue
> -
>
> Key: EAGLE-380
> URL: https://issues.apache.org/jira/browse/EAGLE-380
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> We may solve this issue in the following way:
> 1. if "eagle" is in doc page title, change it to "Apache Eagle (incubating)".
> 2. if there are many "eagle"s appear in the doc page content, change the 
> first mention of it to "Apache Eagle (incubating, called Eagle in the 
> following)".
> 3. change logo size or position.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-376) skip faulty hbase related UT code

[Michael Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Wu updated EAGLE-376:
-
Description: 
Add the reason for doing this: 

There we found some Unit Test cases for testing against embedded hbase, which 
usually failed due to the unstable performance of embedded hbase (setup for 
some unit test). They often made CI jobs timeout and as a result, compromised 
the exposure of true problems of other components test cases. For the testing 
target of these faulty cases have been tested well for a long time, we decide 
to just ignore them and give the CI jobs chances to expose TRUE failures if 
there is any.

  was:There we found some Unit Test cases for testing against embedded hbase, 
which usually failed due to the unstable performance of embedded hbase (setup 
for some unit test). They often made CI jobs timeout and as a result, 
compromised the exposure of true problems of other components test cases. For 
the testing target of these faulty cases have been tested well for a long time, 
we decide to just ignore them and give the CI jobs chances to expose TRUE 
failures if there is any.


> skip faulty hbase related UT code
> -
>
> Key: EAGLE-376
> URL: https://issues.apache.org/jira/browse/EAGLE-376
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> Add the reason for doing this: 
> There we found some Unit Test cases for testing against embedded hbase, which 
> usually failed due to the unstable performance of embedded hbase (setup for 
> some unit test). They often made CI jobs timeout and as a result, compromised 
> the exposure of true problems of other components test cases. For the testing 
> target of these faulty cases have been tested well for a long time, we decide 
> to just ignore them and give the CI jobs chances to expose TRUE failures if 
> there is any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-376) skip faulty hbase related UT code

[Michael Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Wu updated EAGLE-376:
-
Description: There we found some Unit Test cases for testing against 
embedded hbase, which usually failed due to the unstable performance of 
embedded hbase (setup for some unit test). They often made CI jobs timeout and 
as a result, compromised the exposure of true problems of other components test 
cases. For the testing target of these faulty cases have been tested well for a 
long time, we decide to just ignore them and give the CI jobs chances to expose 
TRUE failures if there is any.  (was: There we found some Unit Test cases for 
testing against embedded hbase, which usually failed due to the unstable 
performance of embedded hbase. They often made CI jobs timeout and as a result, 
compromised the exposure of true problems of other components test cases. For 
the testing target of these faulty cases have been tested well for a long time, 
we decide to just ignore them and give the CI jobs chances to expose TRUE 
failures if there is any.)

> skip faulty hbase related UT code
> -
>
> Key: EAGLE-376
> URL: https://issues.apache.org/jira/browse/EAGLE-376
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> There we found some Unit Test cases for testing against embedded hbase, which 
> usually failed due to the unstable performance of embedded hbase (setup for 
> some unit test). They often made CI jobs timeout and as a result, compromised 
> the exposure of true problems of other components test cases. For the testing 
> target of these faulty cases have been tested well for a long time, we decide 
> to just ignore them and give the CI jobs chances to expose TRUE failures if 
> there is any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-376) skip faulty hbase related UT code

[Michael Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Wu updated EAGLE-376:
-
Description: There we found some Unit Test cases for testing against 
embedded hbase, which usually failed due to the unstable performance of 
embedded hbase. They often made CI jobs timeout and as a result, compromised 
the exposure of true problems of other components test cases. For the testing 
target of these faulty cases have been tested well for a long time, we decide 
to just ignore them and give the CI jobs chances to expose TRUE failures if 
there is any.

> skip faulty hbase related UT code
> -
>
> Key: EAGLE-376
> URL: https://issues.apache.org/jira/browse/EAGLE-376
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> There we found some Unit Test cases for testing against embedded hbase, which 
> usually failed due to the unstable performance of embedded hbase. They often 
> made CI jobs timeout and as a result, compromised the exposure of true 
> problems of other components test cases. For the testing target of these 
> faulty cases have been tested well for a long time, we decide to just ignore 
> them and give the CI jobs chances to expose TRUE failures if there is any.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-383) create scripts to facilitate release process

[Michael Wu (JIRA)]

Michael Wu created EAGLE-383:


 Summary: create scripts to facilitate release process
 Key: EAGLE-383
 URL: https://issues.apache.org/jira/browse/EAGLE-383
 Project: Eagle
  Issue Type: Task
Reporter: Michael Wu
Assignee: Michael Wu


First phase is to make a CLI for committers to automate the process of release, 
which includes following steps:
1. check completion status of jira tickets that point to a fix release version.
2. send notification emails to owner of tickets.
3. send code freezing and branching notification emails to appropriate mailing 
list.
4. status code check: binary files, license, etc.
5. check builds.
6. make tar balls, sign them, generate check-sums, and upload all to the public 
directory for voting review.
7. communicate with git: create tags, etc.
8. send vote emails.
9. send release.
10. send announcement.
11. post release works, such as closing jira version, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #267: Eagle 376 skip false failing hbase related UT co...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/267
  
LGTM for this pr


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-382) Monitoring Application Framework

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384045#comment-15384045
 ] 

ASF GitHub Bot commented on EAGLE-382:
--

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/270

EAGLE-382 Monitoring Application Framework

https://issues.apache.org/jira/browse/EAGLE-382

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

$ git pull https://github.com/haoch/incubator-eagle EAGLE-382

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

https://github.com/apache/incubator-eagle/pull/270.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 #270


commit 769c9b452d71b0f45cc5c828f560c82d602e665e
Author: Hao Chen 
Date:   2016-07-08T03:06:35Z

snapshot. refactoring app-manager framework

commit c6c9a7f768c55123713f395cb36dcdf73ed428c7
Author: Hao Chen 
Date:   2016-07-11T16:46:50Z

Add app entities

commit 64ab8403dfb05106aa02d5bdb65aedc82930016b
Author: Hao Chen 
Date:   2016-07-12T10:12:10Z

Implement persistence framework to decouple repository interface with 
different persistence implementation

commit 2b9d55d92fa196e5139a3a295d687b1d3358fb2c
Author: Hao Chen 
Date:   2016-07-12T14:32:11Z

Integrate google-guice

commit 00da4db21ec825d1aec386cb0ec20b64cbde9c9c
Author: Hao Chen 
Date:   2016-07-13T10:23:43Z

Decouple eagle-server and initialize eagle-app-example

commit a186e25185f070e9db006e2cf629c69ddb8218cb
Author: Hao Chen 
Date:   2016-07-19T12:13:49Z

EAGLE-382 Refactored ApplicationProvider and ApplicationProviderService




> Monitoring Application Framework
> 
>
> Key: EAGLE-382
> URL: https://issues.apache.org/jira/browse/EAGLE-382
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0, v0.4.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #270: EAGLE-382 Monitoring Application Framewor...

[haoch]

GitHub user haoch opened a pull request:

https://github.com/apache/incubator-eagle/pull/270

EAGLE-382 Monitoring Application Framework

https://issues.apache.org/jira/browse/EAGLE-382

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

$ git pull https://github.com/haoch/incubator-eagle EAGLE-382

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

https://github.com/apache/incubator-eagle/pull/270.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 #270


commit 769c9b452d71b0f45cc5c828f560c82d602e665e
Author: Hao Chen 
Date:   2016-07-08T03:06:35Z

snapshot. refactoring app-manager framework

commit c6c9a7f768c55123713f395cb36dcdf73ed428c7
Author: Hao Chen 
Date:   2016-07-11T16:46:50Z

Add app entities

commit 64ab8403dfb05106aa02d5bdb65aedc82930016b
Author: Hao Chen 
Date:   2016-07-12T10:12:10Z

Implement persistence framework to decouple repository interface with 
different persistence implementation

commit 2b9d55d92fa196e5139a3a295d687b1d3358fb2c
Author: Hao Chen 
Date:   2016-07-12T14:32:11Z

Integrate google-guice

commit 00da4db21ec825d1aec386cb0ec20b64cbde9c9c
Author: Hao Chen 
Date:   2016-07-13T10:23:43Z

Decouple eagle-server and initialize eagle-app-example

commit a186e25185f070e9db006e2cf629c69ddb8218cb
Author: Hao Chen 
Date:   2016-07-19T12:13:49Z

EAGLE-382 Refactored ApplicationProvider and ApplicationProviderService




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-382) Monitoring Application Framework

[Hao Chen (JIRA)]

Hao Chen created EAGLE-382:
--

 Summary: Monitoring Application Framework
 Key: EAGLE-382
 URL: https://issues.apache.org/jira/browse/EAGLE-382
 Project: Eagle
  Issue Type: New Feature
Affects Versions: v0.3.0, v0.4.0
Reporter: Hao Chen
Assignee: Hao Chen
 Fix For: v0.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle issue #267: Eagle 376 skip false failing hbase related UT co...

[anyway1021]

Github user anyway1021 commented on the issue:

https://github.com/apache/incubator-eagle/pull/267
  
@qingwen220 this PR and jira ticket is not for fixing problems of siddhi, 
it's just for skipping hbase related UT cases. The failure you pasted is out of 
the scope of it. I'll try to research and fix them in another thread. 

Could you re-consider your judgement based on the above? Thanks.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-358) add help for 404 error on Eagle UI

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383792#comment-15383792
 ] 

ASF GitHub Bot commented on EAGLE-358:
--

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/253#discussion_r71292208
  
--- Diff: eagle-assembly/src/main/README.md ---
@@ -91,6 +91,9 @@ Sandbox Starter

 * check eagle UI 
 
+If you get a 404 Error when trying to access the UI, add port 9099 to 
"Settings->Network->Advanced->Port Forwarding" in VirtualBox.
+(Instruction #4 in 
https://eagle.incubator.apache.org/docs/quick-start.html)
--- End diff --

Seems should be: 
(step 4 in "Setup Hadoop Environment" section on page 
https://eagle.incubator.apache.org/docs/quick-start.html)

"Instruction #4 ..." does not point to the position clearly.


> add help for 404 error on Eagle UI
> --
>
> Key: EAGLE-358
> URL: https://issues.apache.org/jira/browse/EAGLE-358
> Project: Eagle
>  Issue Type: Improvement
> Environment: Horton Sandbox, Virtualbox
>Reporter: Peter Kim
>Priority: Minor
>  Labels: documentation, easyfix
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> I've noticed that some people, including myself, were running into an 404 
> error when trying to access the Eagle UI after successfully finishing 
> examples/eagle-sandbox-starter.sh
> The README.md doesn't explain this but this can be fixed with a simple 
> addition of port 9099 to the virtualbox port forwarding rules (instruction #4 
> on https://eagle.incubator.apache.org/docs/quick-start.html)
> I felt like this should be included/referenced in the final README.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request #253: EAGLE-358 add help for 404 error on Eagle...

[anyway1021]

Github user anyway1021 commented on a diff in the pull request:

https://github.com/apache/incubator-eagle/pull/253#discussion_r71292208
  
--- Diff: eagle-assembly/src/main/README.md ---
@@ -91,6 +91,9 @@ Sandbox Starter

 * check eagle UI 
 
+If you get a 404 Error when trying to access the UI, add port 9099 to 
"Settings->Network->Advanced->Port Forwarding" in VirtualBox.
+(Instruction #4 in 
https://eagle.incubator.apache.org/docs/quick-start.html)
--- End diff --

Seems should be: 
(step 4 in "Setup Hadoop Environment" section on page 
https://eagle.incubator.apache.org/docs/quick-start.html)

"Instruction #4 ..." does not point to the position clearly.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle issue #267: Eagle 376 skip false failing hbase related UT co...

[qingwen220]

Github user qingwen220 commented on the issue:

https://github.com/apache/incubator-eagle/pull/267
  
@anyway1021 I found the following log in Jenkins log

Results :

Failed tests: 
  testSlideWindow1(org.apache.eagle.alert.siddhi.TestSiddhiSlideWindow)

Tests in error: 
  
testTimeSlideWindow(org.apache.eagle.alert.state.TestSiddhiStateSnapshotAndRestore)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Web site branding

[Michael Wu]

@ Julian, or you may give your further comments on ticket EAGLE-380
. Thanks.

On Tue, Jul 19, 2016 at 3:28 PM, Michael Wu  wrote:

> Hi Julian,
>
> Could you take a look at the 1st (disclaimer more prominent) and 3rd
> (remove forking flag) topic in the last sending, please? I may need your
> confirmation to make it clear in my mind, thanks a lot!
>
> Michael
>
> On Mon, Jul 18, 2016 at 5:09 PM, Michael Wu  wrote:
>
>> @Julian,
>>
>> (copy my reply from another thread and paste it as below)
>>
>> Just copy your comments here and adding my comments. Thank you for the
>> suggestions.
>>
>> [Julian] - Also, make the disclaimer more prominent on the front page. It
>> is buried at the bottom of a very long page. I think it should appear in
>> the first screen-full.
>> [Michael] - a find an example from Apache Blur Incubating, do you mean
>> something similar to its disclaimer appears on front page? Such as:
>> http://incubator.apache.org/blur/.
>>
>> [Julian] - In the docs, qualify all Apache projects with Apache. I think
>> you can skip "Apache" in the tag line "Secure Hadoop in real time" but you
>> must acknowledge trademarks.
>> [Michael] -
>> 1. in the new site doc, I have added "Apache" preceding first mention of
>> "eagle" on every page, and commented the following "Eagle" on the page is
>> pointing to "Apache Eagle (incubating)".
>> 2. "acknowledge trademarks", do you mean the trademarks of "hadoop". If I
>> understand right, the "tag line" you mentioned has been modified, it would
>> never mention "Hadoop" again.
>>
>> [Julian] - In the docs, remove "fork me on github" from the top right
>> corner. The call to action is to join the Apache community.
>> [Michael] - Not quite clear with this tip. I'm wondering, where is the
>> appropriate position for us to place the "forking" element on the page? As
>> least, people may contribute by firstly forking a git repository. Do you
>> think the top-nav tag bar is good to add forking components?
>>
>>
>> Thanks.
>> Michael
>>
>> On Mon, Jul 18, 2016 at 4:02 PM, Julian Hyde  wrote:
>>
>>> I added the following comments to the JIRA case:
>>>
>>> * Also, make the disclaimer more prominent on the front page. It is
>>> buried at the bottom of a very long page. I think it should appear in the
>>> first screen-full.
>>>
>>> * Apply these guidelines throughout the site, in particular to the docs,
>>> https://eagle.incubator.apache.org/docs/.
>>>
>>> * In the docs, qualify all Apache projects with Apache. I think you can
>>> skip "Apache" in the tag line "Secure Hadoop in real time" but you must
>>> acknowledge trademarks.
>>>
>>> * In the docs, remove "fork me on github" from the top right corner. The
>>> call to action is to join the Apache community.
>>>
>>> Julian
>>>
>>> > On Jul 17, 2016, at 8:32 PM, Michael Wu  wrote:
>>> >
>>> > BTW, here is a jira ticket for trying to fix this issue: EAGLE-380
>>> > . It'll be thankful
>>> to see
>>> > your comments on it. :)
>>> >
>>> > On Mon, Jul 18, 2016 at 11:29 AM, Michael Wu 
>>> wrote:
>>> >
>>> >> Hi guys,
>>> >>
>>> >> To my understanding on your suggestions, we could modify our docs in
>>> the
>>> >> following ways, please help review if they are satisfying the request:
>>> >> 1. if "eagle" is in doc page title, change it to "Apache Eagle
>>> >> (incubating)".
>>> >> 2. if there are many "eagle"s appear in the doc page content, change
>>> the
>>> >> first mention of it to "Apache Eagle (incubating, called Eagle in the
>>> >> following)".
>>> >> 3. change logo size or position.
>>> >>
>>> >> Anything missed, please DO correct me. Thanks.
>>> >> Michael
>>> >>
>>> >>
>>> >> On Thu, Jun 30, 2016 at 11:05 PM, Henry Saputra <
>>> henry.sapu...@gmail.com>
>>> >> wrote:
>>> >>
>>> >>> Yeah, thinking moving the link and incubator logo up in the header
>>> and
>>> >>> keep
>>> >>> the incubator disclaimer as footer.
>>> >>>
>>> >>> Also move some content in between to separate page to make visitor
>>> scroll
>>> >>> less for homepage.
>>> >>>
>>> >>> Thoughts?
>>> >>>
>>> >>> - Henry
>>> >>>
>>> >>> On Thu, Jun 30, 2016 at 6:31 PM, John D. Ament <
>>> johndam...@apache.org>
>>> >>> wrote:
>>> >>>
>>> 
>>> 
>>>  On 2016-06-29 20:48 (-0400), Henry Saputra >> >
>>>  wrote:
>>> > Probably we could move this section to Powered By Eagle page so
>>> >>> homepage
>>> > could be more clear it is part of ASF and also include Incubator
>>> > description on top of page.
>>> 
>>>  So you're thinking about moving some of the ASF logos up, not
>>> buried in
>>>  the footer?
>>> 
>>> >
>>> > On Thursday, June 30, 2016, arunkarthick m >> >
>>>  wrote:
>>> >
>>> >> The eBay logo and Paypal logo under who uses Eagle part is taking
>>> up
>>>  too
>>> >> much screen space. Apart from that ebay is mentioned only in one
>>> >>> place.
>>> >>
>>> >> Thanks,
>>> >> Arun

[jira] [Commented] (EAGLE-380) fix eagle site/doc branding issue

[Michael Wu (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383730#comment-15383730
 ] 

Michael Wu commented on EAGLE-380:
--

[~julianhyde]

To your comments: 
1. "Also, make the disclaimer more prominent on the front page. It is buried at 
the bottom of a very long page. I think it should appear in the first 
screen-full."
[Michael] - I find an example from Apache Blur Incubating, do you mean 
something similar to its disclaimer appears on front page? Such as: 
http://incubator.apache.org/blur/.

2. "In the docs, qualify all Apache projects with Apache. I think you can skip 
"Apache" in the tag line "Secure Hadoop in real time" but you must acknowledge 
trademarks."
[Michael] - 
  a) in the new site doc, I have added "Apache" preceding first mention of 
"eagle" on every page, and commented the following "Eagle" on the page is 
pointing to "Apache Eagle (incubating)". 
  b) "acknowledge trademarks", do you mean the trademarks of "hadoop". If I 
understand right, the "tag line" you mentioned has been modified, it would 
never mention "Hadoop" again.

3. "In the docs, remove 'fork me on github' from the top right corner. The call 
to action is to join the Apache community."
[Michael] - Not quite clear with this tip. I'm wondering, where is the 
appropriate position for us to place the "forking" element on the page? As 
least, people may contribute by firstly forking a git repository. Do you think 
the top-nav tag bar is good to add forking components?

Could you please confirm my understandings on them? Thanks.

> fix eagle site/doc branding issue
> -
>
> Key: EAGLE-380
> URL: https://issues.apache.org/jira/browse/EAGLE-380
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> We may solve this issue in the following way:
> 1. if "eagle" is in doc page title, change it to "Apache Eagle (incubating)".
> 2. if there are many "eagle"s appear in the doc page content, change the 
> first mention of it to "Apache Eagle (incubating, called Eagle in the 
> following)".
> 3. change logo size or position.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Web site branding

[Michael Wu]

Hi Julian,

Could you take a look at the 1st (disclaimer more prominent) and 3rd
(remove forking flag) topic in the last sending, please? I may need your
confirmation to make it clear in my mind, thanks a lot!

Michael

On Mon, Jul 18, 2016 at 5:09 PM, Michael Wu  wrote:

> @Julian,
>
> (copy my reply from another thread and paste it as below)
>
> Just copy your comments here and adding my comments. Thank you for the
> suggestions.
>
> [Julian] - Also, make the disclaimer more prominent on the front page. It
> is buried at the bottom of a very long page. I think it should appear in
> the first screen-full.
> [Michael] - a find an example from Apache Blur Incubating, do you mean
> something similar to its disclaimer appears on front page? Such as:
> http://incubator.apache.org/blur/.
>
> [Julian] - In the docs, qualify all Apache projects with Apache. I think
> you can skip "Apache" in the tag line "Secure Hadoop in real time" but you
> must acknowledge trademarks.
> [Michael] -
> 1. in the new site doc, I have added "Apache" preceding first mention of
> "eagle" on every page, and commented the following "Eagle" on the page is
> pointing to "Apache Eagle (incubating)".
> 2. "acknowledge trademarks", do you mean the trademarks of "hadoop". If I
> understand right, the "tag line" you mentioned has been modified, it would
> never mention "Hadoop" again.
>
> [Julian] - In the docs, remove "fork me on github" from the top right
> corner. The call to action is to join the Apache community.
> [Michael] - Not quite clear with this tip. I'm wondering, where is the
> appropriate position for us to place the "forking" element on the page? As
> least, people may contribute by firstly forking a git repository. Do you
> think the top-nav tag bar is good to add forking components?
>
>
> Thanks.
> Michael
>
> On Mon, Jul 18, 2016 at 4:02 PM, Julian Hyde  wrote:
>
>> I added the following comments to the JIRA case:
>>
>> * Also, make the disclaimer more prominent on the front page. It is
>> buried at the bottom of a very long page. I think it should appear in the
>> first screen-full.
>>
>> * Apply these guidelines throughout the site, in particular to the docs,
>> https://eagle.incubator.apache.org/docs/.
>>
>> * In the docs, qualify all Apache projects with Apache. I think you can
>> skip "Apache" in the tag line "Secure Hadoop in real time" but you must
>> acknowledge trademarks.
>>
>> * In the docs, remove "fork me on github" from the top right corner. The
>> call to action is to join the Apache community.
>>
>> Julian
>>
>> > On Jul 17, 2016, at 8:32 PM, Michael Wu  wrote:
>> >
>> > BTW, here is a jira ticket for trying to fix this issue: EAGLE-380
>> > . It'll be thankful
>> to see
>> > your comments on it. :)
>> >
>> > On Mon, Jul 18, 2016 at 11:29 AM, Michael Wu 
>> wrote:
>> >
>> >> Hi guys,
>> >>
>> >> To my understanding on your suggestions, we could modify our docs in
>> the
>> >> following ways, please help review if they are satisfying the request:
>> >> 1. if "eagle" is in doc page title, change it to "Apache Eagle
>> >> (incubating)".
>> >> 2. if there are many "eagle"s appear in the doc page content, change
>> the
>> >> first mention of it to "Apache Eagle (incubating, called Eagle in the
>> >> following)".
>> >> 3. change logo size or position.
>> >>
>> >> Anything missed, please DO correct me. Thanks.
>> >> Michael
>> >>
>> >>
>> >> On Thu, Jun 30, 2016 at 11:05 PM, Henry Saputra <
>> henry.sapu...@gmail.com>
>> >> wrote:
>> >>
>> >>> Yeah, thinking moving the link and incubator logo up in the header and
>> >>> keep
>> >>> the incubator disclaimer as footer.
>> >>>
>> >>> Also move some content in between to separate page to make visitor
>> scroll
>> >>> less for homepage.
>> >>>
>> >>> Thoughts?
>> >>>
>> >>> - Henry
>> >>>
>> >>> On Thu, Jun 30, 2016 at 6:31 PM, John D. Ament > >
>> >>> wrote:
>> >>>
>> 
>> 
>>  On 2016-06-29 20:48 (-0400), Henry Saputra 
>>  wrote:
>> > Probably we could move this section to Powered By Eagle page so
>> >>> homepage
>> > could be more clear it is part of ASF and also include Incubator
>> > description on top of page.
>> 
>>  So you're thinking about moving some of the ASF logos up, not buried
>> in
>>  the footer?
>> 
>> >
>> > On Thursday, June 30, 2016, arunkarthick m 
>>  wrote:
>> >
>> >> The eBay logo and Paypal logo under who uses Eagle part is taking
>> up
>>  too
>> >> much screen space. Apart from that ebay is mentioned only in one
>> >>> place.
>> >>
>> >> Thanks,
>> >> Arun
>> >>
>> >> On Wed, Jun 29, 2016 at 2:40 PM, Julian Hyde > >> > wrote:
>> >>
>> >>> Check what the branding guide says. I think only the first
>> >>> occurrence
>> >>> needs to be fully-qualified.
>> >>>
>> >>> But also ask yourself: Does this page make it look like the
>> >>> project
>>  is
>> >>> controlled by a parti

[GitHub] incubator-eagle pull request #269: add PGP pub-key of anyway1021

[anyway1021]

GitHub user anyway1021 opened a pull request:

https://github.com/apache/incubator-eagle/pull/269

add PGP pub-key of anyway1021 



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

$ git pull https://github.com/anyway1021/incubator-eagle add-pgp-key

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

https://github.com/apache/incubator-eagle/pull/269.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 #269


commit fca6122115b07ff180319e2ef0b243cb546d86be
Author: anyway1021 
Date:   2016-07-19T06:59:40Z

add PGP pub-key of anyway1021 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---