[GitHub] incubator-rocketmq issue #118: [ROCKETMQ-28] Encrypt transmission layer.

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/incubator-rocketmq/pull/118
  

[![Coverage 
Status](https://coveralls.io/builds/12231167/badge)](https://coveralls.io/builds/12231167)

Coverage increased (+0.3%) to 38.725% when pulling 
**0ca60db50aec2abc3ad3c3ea4a92e838a7579734 on lizhanhui:tls** into 
**c4a3e0c1325e67aec76aa94e9ade3a6ea1b682d2 on apache:develop**.



---
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-rocketmq issue #49: [ROCKETMQ-72] DefaultMessageStore cannot be pr...

[vongosling]

Github user vongosling commented on the issue:

https://github.com/apache/incubator-rocketmq/pull/49
  
What's going on 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.
---

[GitHub] incubator-rocketmq issue #126: [ROCKETMQ-231] fix pull consumer pull result ...

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/incubator-rocketmq/pull/126
  

[![Coverage 
Status](https://coveralls.io/builds/12228663/badge)](https://coveralls.io/builds/12228663)

Coverage increased (+0.5%) to 39.59% when pulling 
**bc492f514052673c9f80ff1b156ab301fabb0983 on 
lindzh:fix_consumer_pull_msg_size** into 
**c297258d219277c932a84d37fec19aeaea54588a on apache:master**.



---
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: Failed to generate JavaDoc

[Zhanhui Li]

Hi Ruijie,

Glad that you are interested in RocketMQ.

Could you please detail the problem you met? What kind of errors are shown? 
Actually, I just ran a test of generating javadoc and there are indeed some 
warnings complaining missing of parameters or invalid @param. However, there is 
no error in my test run. Could you please double-check and report more specific 
error details if there were any?


Zhanhui Li

> 在 2017年7月2日，下午11:18，瑞杰  写道：
> 
> Hi all,
> 
> 
>I am investigating RocketMQ, and I tried to generate JavaDoc by Idea 14.
> But this process raised a lot of errors and warnings, is that a known problem 
> or
> I did not set it in correct way?
> 
> 
> ruijie

[GitHub] incubator-rocketmq-externals pull request #25: update to 1.0.0 verison

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-rocketmq-externals/pull/25


---
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: Apache RocketMQ Meetup Beijing Full Review

[Von Gosling]

Very nice, looking forward to more RocketMQ’s community guys to  share their 
experience in Messaging and Streaming next time :-)


Von Gosling


> 在 2017年7月2日，00:15，yukon  写道：
> 
> Hi guys,
> 
> Apache RocketMQ Meetup Beijing concluded with a perfect ending. Thanks for 
> everyone's participation. 
> 
> We are really appreciate that over 300 RocketMQ or open source enthusiasts 
> gathered in Institute of Software, Chinese Academy of Sciences, to attend 
> this meetup in this hot summer day.
> 
> 
> ​
> 
> Let us make a simple summary for this meetup. More details please refer to 
> our live streaming with photos and words: https://twitter.com/ApacheRocketMQ 
> 
> 
> The opening:
> 
> Our emcee introduced the history of RocketMQ, the road traveled from Alibaba 
> to Apache foundation, and global user distribution of Apache RocketMQ.
> 
> 
> 
> 
> 
> Topic: Best practice for Apache RocketMQ
> 
> The speaker lollipop(RocketMQ Committer/PMC Member) shared core features and 
> best practices of RocketMQ.
> 
> 
> 
> Topic: Apache RocketMQ UseCase
> 
> ​ lizhanhui(RocketMQ Committer/PMC Member)'s presentation focused on 
> extensible, scalable, developer skill set of Apache RocketMQ.
> 
> 
> ​
> Topic: Performance and BigData Ecosystem
> 
> dongeforever(RocketMQ Committer) is introduced the ecosystem of Apache 
> RocketMQ, and how to integrate with other community.
> 
> 
> ​
> Topic: Performance Tuning in RocketMQ
> 
> The speaker yukon(RocketMQ Committer/PMC Member) shared the low latency and 
> high throughput secrets of Apache RocketMQ.
> 
> ​
> 
> Topic: Streaming and Messaging
> 
> Xin Wang(Apache Storm Committer/PMC member)'s topic covered the relations 
> between streaming and messaging platform, and the challenges and tips in 
> Storm usage.
> 
> 
> ​
> 
> Topic: RocketMQ-MySQL-Replicator
> 
> Qun Zhao(RocketMQ Top Contributor) brought a new community project for us, 
> RocketMQ-MySQL-Replicator. 
> ​
> 
> 
> ​
> ​Topic: Messaging Community and Ecosystem
> 
> vongosling(RocketMQ Core-creator, Committer/PMC member)'s topic *Messaging 
> Community and Ecosystem* mainly focused on our comprehension of Apache way 
> and how to build a healthy Apache community.
> 
> 
> 
> More details please refer to our live streaming with photos and words: 
> https://twitter.com/ApacheRocketMQ 
> 
> Regards,
> yukon

[GitHub] incubator-rocketmq pull request #110: [ROCKETMQ-208]incompatibility problem ...

[Jaskey]

Github user Jaskey closed the pull request at:

https://github.com/apache/incubator-rocketmq/pull/110


---
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.
---