Re: Travis CI failed

2018-09-09 Thread yuhang xiu
Hi, I also checked the log just now and found no problems. I have restarted this task, I will observe the results after a while. YunKun Huang 于2018年9月10日周一 下午1:53写道: > Check this log, it says compile fail on dubbo-common module: > https://travis-ci.org/apache/incubator-dubbo/jobs/426109384 > >

Re: Travis CI failed

2018-09-09 Thread Jerrick Zhu
On Mon, Sep 10, 2018 at 1:53 PM YunKun Huang wrote: > Check this log, it says compile fail on dubbo-common module: > https://travis-ci.org/apache/incubator-dubbo/jobs/426109384 > > But there is no code change since latest successful bulid. > Also I try to run build in my local, it pass with jdk

Re: Travis CI failed

2018-09-09 Thread YunKun Huang
Check this log, it says compile fail on dubbo-common module: https://travis-ci.org/apache/incubator-dubbo/jobs/426109384 But there is no code change since latest successful bulid. Also I try to run build in my local, it pass with jdk 8. On 2018/09/10 05:36:27, Jerrick Zhu wrote: > Hi,

Travis CI failed

2018-09-09 Thread Jerrick Zhu
Hi, community I found that all travis CI builds failed on Java8. Here is the master's build: https://travis-ci.org/apache/incubator-dubbo Anyone can help to check it?

Re: [Discuss]Prepare for the next release v2.6.4

2018-09-09 Thread Jun Liu
> Do you think we need another one to be the release manager? In case > that we can make sure our release guide works perfectly. Yes, I think we need a new manager to do the next release, to get familiar with and improve the release process. But I'm not sure if anyone has committer privilege is

Re:Re: Dubbo document update registry's group attribute description

2018-09-09 Thread 凝雨
ops issue: https://github.com/apache/incubator-dubbo-ops/issues/103 What is the progress of OPS reconstruction at present? 在 2018-09-08 22:47:30,"Ian Luo" 写道: >great. I noticed the PR made against website has been merged. What about >ops? > >On Sat, Sep 8, 2018 at 10:47 AM 凝雨 wrote: > >>

Re: The effect of Provider async on the Consumer side

2018-09-09 Thread yuhang xiu
Hi Huxing, This is because there is a bug that causes them to be inconsistent. We removed the async attribute from the Provider in ClusterUtil, but did not remove the method.async attribute, causing the Provider's method.async to affect the Consumer side. We don't need extra configuration, we