Re: [Proposal] Dubbo Shanghai Meetup
+1, it's good for building up developer relationship and strong community, let's do it. On Thu, Jun 14, 2018 at 11:46 PM Huxing Zhang wrote: > Hi Dubbo PMC, > > I am requesting the PMC for the approval of holding a half-day meetup > in Shanghai to build the community and provide a way to listen to end > users in order to make Dubbo better. > > * What is the topic focus of the event? > Topics including status of Dubbo, Dubbo with cloud native, Dubbo > eco-system, and user practices for using Dubbo. Details are listed > below. > > * Who is organising the event > PMCs of Apache Dubbo (incubating) > > * When is the event > 2018.6.23 13:00-17:15 > > * How many attendees are expected > 200~400 > > * How much PMC involvement is there already > PMC are responsible to decide the topics. > > * Which marks are requested > Name of "Apache Dubbo (Incubating)" > > * How will the event selection work? > Topics will be selected by the Dubbo PMC > > * Is this for profit or non-profit? > Non-profit > > I am following [1] for the procedure. > > [1] http://community.apache.org/events/small-events.html > > > Below is a detailed agenda for the meetup. > > ## Date > > 2018.6.23 13:00-17:15 > > ## Venue > > International Roadshow Hall, 1st floor, No. 800 Naxian Road > Zhangjiang International Innovation Harbor, Pudong Xinqu District, Shanghai > 浦东新区纳贤路800号张江国际创新港 一楼（国际路演厅） > > ## Schedule > > 13:00-14:00 Check-in > 14:00-14:45 Apache Dubbo(incubating) Open Source Status and Roadmap(Yong > Zhu) > 14:45-15:30 Thoughts of Dubbo Cloud Native (Mercy Ma) > 15:30-15:45 Tea break > 15:45-16:30 Nacos - Contribute to Dubbo Ecology, Alibaba Service Registry > and > Configuration Center Open Source Initiative (Guo Ping) > 16:30-17:15 Internet financial with dubbo (Zhiwei Pan) > > ## Detailed Description > > Topic: > Apache Dubbo(incubating) Open Source Status and Roadmap > > Abstract: > Dubbo is a distributed RPC framework developed by Alibaba, which > has been favored by developers since it was opened in 2012 and has been > widely used in service solutions. Now there has nearly 20,000 stars on > github after remaintenance, with a huge response in the community. This > topic brings you the recent works as well as some thoughts with the > roadmap. > > Speaker Bio: > Yong Zhu(Jerrick), senior technical expert of Alibaba, developer > of Dubbo, MicroServices framework. > > - > Topic: > Thoughts of Dubbo Cloud Native > > Abstract: > Discuss about Dubbo Cloud Native that includes introduction to Dubbo > Spring Boot Project, integration with Spring Cloud, and some thoughts > of supporting popular CNCF projects. > > Speaker Bio: > Mercy Ma (mercyblitz), Technical expert of Alibaba, developer of > Apache Dubbo, work at Micro-Services Architecture involving > infrastructure build and technical integration. > > - > Topic: > Nacos - Contribute to Dubbo Ecology, Alibaba Service Registry and > Configuration Center Open Source Initiative > > Abstract: > Shares the new challenges faced by the service registration center and > service configuration management in the modern application service-centric > architecture in the cloud era, and the latest open source project Nacos. > > Speaker Bio: > Guo Ping (Penn), senior technical expert of Alibaba, head of the product > line of soft load and configuration center, led the team to build Alibaba's > soft load balancing system and operates the world's largest production > configuration center system. Currently, he is also responsible for the ACM > cloud application configuration management products ACM and ANS (EDAS > component market). > > - > Topic: > Internet financial with dubbo > > Abstract: > How to use Dubbo to split and manage services during the rapid > development of Internet Finance > > Speaker Bio: > Zhiwei Pan, 上海融之家金融信息服务有限公司 > > Thank Alibaba for sponsoring this event. > > -- > Best Regards！ > Huxing >
Re: Planing to rename dubbo package to org.apache
merged, now it is critical to provide dubbo compatibility package as soon as possible, since the current code base will effect existing dubbo samples and dubbo apps. BTW, +1 to maven groupId change without doubt. Thanks, -Ian. On Fri, Jun 15, 2018 at 2:23 PM Yong Zhu wrote: > Since the pacakge has been rename to org.apache, new PRs can be sent with > confidence. > > Next step, I'll add dubbo-compatible. > > Another question, I suggest rename groupId to org.apache with this big > change, What do you think? > > On Thu, Jun 14, 2018 at 9:25 AM Yong Zhu wrote: > > > Now, I'll start to do this task, and then send a PR to master. At the > same > > time, I'll add a new module named "dubbo-compatible" to support old > > extensions, this will take some time. > > > > On Fri, Jun 8, 2018 at 2:09 PM Ian Luo wrote: > > > >> agree, let's address the exiting PRs as soon as possible, to make the > >> renaming package effort easier. > >> > >> -Ian. > >> > >> On Fri, Jun 8, 2018 at 10:31 AM Xin Wang wrote: > >> > >> > >Now, there also have 23 PRs under reviewing, we need to fix them > first, > >> > merge or close it > >> > > >> > I think what we need to do now is to set up a deadline to deal with > >> these > >> > 23 PRs quickly. > >> > > >> > > >> > Jun Liu 于2018年6月8日周五 上午10:04写道： > >> > > >> > > > I suggest that we have to freeze new comming PR after notification > >> > > community. > >> > > > >> > > I don’t think it’s necessary to freeze PRs. > >> > > > >> > > To some extend, it'is the PRs containing pretty much changes that > will > >> > > have most of the compatibility problems. Since currently most of the > >> > > features under progress are developing by the Dubbo team or some > >> > > contributors who keeps a close contact with Dubbo community, we can > >> avoid > >> > > the compatibility problem to the greatest extend. > >> > > > >> > > Even though, we should still make sure that the whole community get > >> fully > >> > > notified of the package rename plan, so they can start or refactor > >> their > >> > > patches based on the codebase before or after rename. > >> > > > >> > > Best regards, > >> > > Jun > >> > > > >> > > > On 7 Jun 2018, at 3:42 PM, Mercy wrote: > >> > > > > >> > > > I suggest that we have to freeze new comming PR after notification > >> > > community. > >> > > > > >> > > > > >> > > > Kind regards, > >> > > > > >> > > > Mercy Ma > >> > > > > >> > > > > >> > > > 在 2018/6/7 下午3:32, Yong Zhu 写道: > >> > > >> Now, there also have 23 PRs under reviewing, we need to fix them > >> > first, > >> > > >> merge or close it. Then we rename the package ASAP. > >> > > > > >> > > > >> > > > >> > > >> > > >
Re: Planing to rename dubbo package to org.apache
Since the pacakge has been rename to org.apache, new PRs can be sent with confidence. Next step, I'll add dubbo-compatible. Another question, I suggest rename groupId to org.apache with this big change, What do you think? On Thu, Jun 14, 2018 at 9:25 AM Yong Zhu wrote: > Now, I'll start to do this task, and then send a PR to master. At the same > time, I'll add a new module named "dubbo-compatible" to support old > extensions, this will take some time. > > On Fri, Jun 8, 2018 at 2:09 PM Ian Luo wrote: > >> agree, let's address the exiting PRs as soon as possible, to make the >> renaming package effort easier. >> >> -Ian. >> >> On Fri, Jun 8, 2018 at 10:31 AM Xin Wang wrote: >> >> > >Now, there also have 23 PRs under reviewing, we need to fix them first, >> > merge or close it >> > >> > I think what we need to do now is to set up a deadline to deal with >> these >> > 23 PRs quickly. >> > >> > >> > Jun Liu 于2018年6月8日周五 上午10:04写道： >> > >> > > > I suggest that we have to freeze new comming PR after notification >> > > community. >> > > >> > > I don’t think it’s necessary to freeze PRs. >> > > >> > > To some extend, it'is the PRs containing pretty much changes that will >> > > have most of the compatibility problems. Since currently most of the >> > > features under progress are developing by the Dubbo team or some >> > > contributors who keeps a close contact with Dubbo community, we can >> avoid >> > > the compatibility problem to the greatest extend. >> > > >> > > Even though, we should still make sure that the whole community get >> fully >> > > notified of the package rename plan, so they can start or refactor >> their >> > > patches based on the codebase before or after rename. >> > > >> > > Best regards, >> > > Jun >> > > >> > > > On 7 Jun 2018, at 3:42 PM, Mercy wrote: >> > > > >> > > > I suggest that we have to freeze new comming PR after notification >> > > community. >> > > > >> > > > >> > > > Kind regards, >> > > > >> > > > Mercy Ma >> > > > >> > > > >> > > > 在 2018/6/7 下午3:32, Yong Zhu 写道: >> > > >> Now, there also have 23 PRs under reviewing, we need to fix them >> > first, >> > > >> merge or close it. Then we rename the package ASAP. >> > > > >> > > >> > > >> > >> >
Re: 服务端收到心跳包的时候不要检查 header 里面的 serialID
The original design allows heartbeat packet to have data included, though the current implementation is in fact an empty packet. You can take a look at com.alibaba.dubbo.remoting.exchange.Response#HEARTBEAT_EVENT, which is set to null right now. If in the future a valid data is required in heartbeat packet, then the current logic for serialID will be necessary. I'd like to listen to others' comments before we decide either to ignore the check or keep the current design. -Ian. On Thu, Jun 14, 2018 at 9:44 PM 风暴角的企鹅 wrote: > Dr All: > 我写了一个 dubbo 原生协议（hessian2）的go语言测试客户端，代码如下： > https://github.com/alexstocks/go-practice/blob/master/hessian/main.go > > > 我构造了一个二进制心跳包对服务端进行测试。 > > > 示例代码中我循环增大serialID从0开始直到其最大值31。其中 serialID 取值 [1, 3, 4, 5, 6, 7] > 时，服务端有以下异常日志： > > > 2018-06-14 14:50:04,598 [New I/O server worker #1-1] WARN > alibaba.dubbo.rpc.protocol.dubbo.DubboCodec (DubboCodec.java:140) - > [DUBBO] Decode request failed: Flag error, expect > OBJECT_NULL|OBJECT_DUMMY|OBJECT_DESC|OBJECT_DESC_ID, get 78, dubbo version: > 2.5.4, current host: 127.0.0.1 > java.io.IOException: Flag error, expect > OBJECT_NULL|OBJECT_DUMMY|OBJECT_DESC|OBJECT_DESC_ID, get 78 > at > com.alibaba.dubbo.common.serialize.support.dubbo.GenericObjectInput.readObject(GenericObjectInput.java:79) > at > com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decodeHeartbeatData(ExchangeCodec.java:381) > at > com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody(DubboCodec.java:121) > at > com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:118) > at > com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:79) > at > com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.decode(DubboCountCodec.java:46) > at > com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:134) > at > org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) > at > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) > at > org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) > at > org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) > at > org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349) > at > org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200) > at > org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at > org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 2018-06-14 14:50:05,599 [New I/O server worker #1-1] WARN > com.alibaba.dubbo.remoting.transport.AbstractServer > (AbstractServer.java:199) - [DUBBO] All clients has discontected from / > 127.0.0.1:2. You can graceful shutdown now., dubbo version: 2.5.4, > current host: 127.0.0.1 > > > > 经过与 dubbo commiter 们讨论，说是这几个 ID 是内部保留的实例ID，如 > https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo-common/src/main/java/com/alibaba/dubbo/common/serialize/support/json/FastJsonSerialization.java > 。 > > > 针对这个例子，这个解释是 okay 的，可以解释这个错误。不过个人建议：服务端收到心跳包的时候不要检查 header 里面的 > serialID，直接放过，可否？ > > > > 因为心跳包不设计逻辑处理，不需要获取serialID对应的实例，这里检查这个字段有什么意义呢？因为这个原因就导致服务端抛出异常，个人觉得这个处理欠妥。
Re: Assigning Github issues to non-committer user
I guess this is the best option we could approach. On Fri, Jun 15, 2018 at 9:59 AM Yunkun Huang wrote: > > I think github only support assign an issue to people with write access, > collaborators on personal projects, or members of same organization with > read permissions on the repository. > > dubbo is under apache organization, so if a user is non-committer user, I > don't think we can assign it to them. maybe just put a comment and let > everyone knows who is working on it. > > On 2018/06/14 08:57:16, Huxing Zhang wrote: > > Hi, > > > > I found that I can not assign issue to a non-committer user. > > > > If some of the user would like to take an issue, how can I assign to > him/her? > > > > -- > > Best Regards！ > > Huxing > > >
Re: About the start error for “dubbo admin”
Now dubbo admin only works under JDK8. So please try it in JDK7 or JDK6. As we are considering do some work on dubbo admin, you can check the prior thread: https://lists.apache.org/thread.html/523f1fefc98c96ae4b0c55b3e8f69e237ca91a0c7c5221dfe247d65f@%3Cdev.dubbo.apache.org%3E On Fri, Jun 15, 2018 at 10:02 AM Yunkun Huang wrote: > Could you try jdk 8? > > There is a similar issue reported on jdk9. I guess jdk10 has the same > issue. > > https://github.com/apache/incubator-dubbo-ops/issues/14 > > On 2018/06/15 01:11:27, "Kakarotto" <1136232...@qq.com> wrote: > > .Dear： > >When I use tomcat to start dubbo admin, report > error（java.lang.IllegalArgumentException: Unknown flag 0x1000）. zookeeper > start ok. > >software version: > >dubbo:2.62 release > >dubbo admin:2.0.0 > >zookeeper:3.4.12 > >tomcat:9.0.9 > >jdk:10.0.1 > > > >error message(localhost.2018-06-15.log): > > > > > > > > > > > > > > 请帮忙看下，我网上找了没发现解决方法，谢谢 >
Re: About the start error for “dubbo admin”
Could you try jdk 8? There is a similar issue reported on jdk9. I guess jdk10 has the same issue. https://github.com/apache/incubator-dubbo-ops/issues/14 On 2018/06/15 01:11:27, "Kakarotto" <1136232...@qq.com> wrote: > .Dear： >When I use tomcat to start dubbo admin, report > error（java.lang.IllegalArgumentException: Unknown flag 0x1000）. zookeeper > start ok. >software version: >dubbo:2.62 release >dubbo admin:2.0.0 >zookeeper:3.4.12 >tomcat:9.0.9 >jdk:10.0.1 > >error message(localhost.2018-06-15.log): > > > > > > > 请帮忙看下，我网上找了没发现解决方法，谢谢
Re: Assigning Github issues to non-committer user
I think github only support assign an issue to people with write access, collaborators on personal projects, or members of same organization with read permissions on the repository. dubbo is under apache organization, so if a user is non-committer user, I don't think we can assign it to them. maybe just put a comment and let everyone knows who is working on it. On 2018/06/14 08:57:16, Huxing Zhang wrote: > Hi, > > I found that I can not assign issue to a non-committer user. > > If some of the user would like to take an issue, how can I assign to him/her? > > -- > Best Regards！ > Huxing >
About the start error for ??dubbo admin??
.Dear?? When I use tomcat to start dubbo admin, report error??java.lang.IllegalArgumentException: Unknown flag 0x1000??. zookeeper start ok. software version: dubbo:2.62 release dubbo admin:2.0.0 zookeeper:3.4.12 tomcat:9.0.9 jdk:10.0.1 error message(localhost.2018-06-15.log): ??
[Proposal] Dubbo Shanghai Meetup
Hi Dubbo PMC, I am requesting the PMC for the approval of holding a half-day meetup in Shanghai to build the community and provide a way to listen to end users in order to make Dubbo better. * What is the topic focus of the event? Topics including status of Dubbo, Dubbo with cloud native, Dubbo eco-system, and user practices for using Dubbo. Details are listed below. * Who is organising the event PMCs of Apache Dubbo (incubating) * When is the event 2018.6.23 13:00-17:15 * How many attendees are expected 200~400 * How much PMC involvement is there already PMC are responsible to decide the topics. * Which marks are requested Name of "Apache Dubbo (Incubating)" * How will the event selection work? Topics will be selected by the Dubbo PMC * Is this for profit or non-profit? Non-profit I am following [1] for the procedure. [1] http://community.apache.org/events/small-events.html Below is a detailed agenda for the meetup. ## Date 2018.6.23 13:00-17:15 ## Venue International Roadshow Hall, 1st floor, No. 800 Naxian Road Zhangjiang International Innovation Harbor, Pudong Xinqu District, Shanghai 浦东新区纳贤路800号张江国际创新港 一楼（国际路演厅） ## Schedule 13:00-14:00 Check-in 14:00-14:45 Apache Dubbo(incubating) Open Source Status and Roadmap(Yong Zhu) 14:45-15:30 Thoughts of Dubbo Cloud Native (Mercy Ma) 15:30-15:45 Tea break 15:45-16:30 Nacos - Contribute to Dubbo Ecology, Alibaba Service Registry and Configuration Center Open Source Initiative (Guo Ping) 16:30-17:15 Internet financial with dubbo (Zhiwei Pan) ## Detailed Description Topic: Apache Dubbo(incubating) Open Source Status and Roadmap Abstract: Dubbo is a distributed RPC framework developed by Alibaba, which has been favored by developers since it was opened in 2012 and has been widely used in service solutions. Now there has nearly 20,000 stars on github after remaintenance, with a huge response in the community. This topic brings you the recent works as well as some thoughts with the roadmap. Speaker Bio: Yong Zhu(Jerrick), senior technical expert of Alibaba, developer of Dubbo, MicroServices framework. - Topic: Thoughts of Dubbo Cloud Native Abstract: Discuss about Dubbo Cloud Native that includes introduction to Dubbo Spring Boot Project, integration with Spring Cloud, and some thoughts of supporting popular CNCF projects. Speaker Bio: Mercy Ma (mercyblitz), Technical expert of Alibaba, developer of Apache Dubbo, work at Micro-Services Architecture involving infrastructure build and technical integration. - Topic: Nacos - Contribute to Dubbo Ecology, Alibaba Service Registry and Configuration Center Open Source Initiative Abstract: Shares the new challenges faced by the service registration center and service configuration management in the modern application service-centric architecture in the cloud era, and the latest open source project Nacos. Speaker Bio: Guo Ping (Penn), senior technical expert of Alibaba, head of the product line of soft load and configuration center, led the team to build Alibaba's soft load balancing system and operates the world's largest production configuration center system. Currently, he is also responsible for the ACM cloud application configuration management products ACM and ANS (EDAS component market). - Topic: Internet financial with dubbo Abstract: How to use Dubbo to split and manage services during the rapid development of Internet Finance Speaker Bio: Zhiwei Pan, 上海融之家金融信息服务有限公司 Thank Alibaba for sponsoring this event. -- Best Regards！ Huxing
Re: [Call for talks]: Dubbo Shanghai meetup
On Thu, Jun 14, 2018 at 10:31 AM, 修宇航 wrote: > Maybe a topic to show the enhancement and new features since the community > re maintain dubbo project? I think the topic you suggested can be covered in the "Apache Dubbo(incubating) Open Source Status and Roadmap" topic. > By the way, does when and where are decieded to meetup in ShangHai? I > will participate! > > 2018-06-07 17:12 GMT+08:00 Huxing Zhang : > >> Hi community, >> >> We are planning to hold a meetup in Shanghai in June 23rd (Saturday) >> or June 24th (Sunday), and we are open to community talks about: >> >> * How we use Dubbo in production system >> * Dubbo best practice >> * Integrate Dubbo with other open source software >> * Other topics involving Dubbo >> >> Please submit your ideas before June 13rd by sending email to >> priv...@dubbo.apache.org >> >> Thank Alibaba for sponsoring this event. >> >> -- >> Best Regards！ >> Huxing >> -- Best Regards！ Huxing
Re: [Call for talks]: Dubbo Shanghai meetup
Hi All, We have received 4 talks from the community, I am going to call a formal proposal for Dubbo Shanghai meetup. On Thu, Jun 14, 2018 at 11:50 AM, Ian Luo wrote: > @carryxyh, here below pls. check Dubbo Shanghai meetup info: > > time: 2018.06.23 afternoon > addr: International Roadshow Hall, 1st floor, No. 800 Naxian Road > Zhangjiang International Innovation Harbor, Pudong Xinqu District. > 地址：浦东新区纳贤路800号张江国际创新港 一楼（国际路演厅） > > > On Thu, Jun 14, 2018 at 10:35 AM 修宇航 wrote: > >> Maybe a topic to show the enhancement and new features since the community >> re maintain dubbo project? >> By the way, does when and where are decieded to meetup in ShangHai? I >> will participate! >> >> 2018-06-07 17:12 GMT+08:00 Huxing Zhang : >> >> > Hi community, >> > >> > We are planning to hold a meetup in Shanghai in June 23rd (Saturday) >> > or June 24th (Sunday), and we are open to community talks about: >> > >> > * How we use Dubbo in production system >> > * Dubbo best practice >> > * Integrate Dubbo with other open source software >> > * Other topics involving Dubbo >> > >> > Please submit your ideas before June 13rd by sending email to >> > priv...@dubbo.apache.org >> > >> > Thank Alibaba for sponsoring this event. >> > >> > -- >> > Best Regards！ >> > Huxing >> > >> -- Best Regards！ Huxing
Re: Project decisions need to be made on list
On Thu, Jun 14, 2018 at 9:50 PM, Mark Thomas wrote: > > > On 14/06/2018 15:36, Huxing Zhang wrote: >> >> On Thu, Jun 14, 2018 at 3:09 PM, Mark Thomas wrote: >>> >>> All, >>> >>> I have seen multiple instances in the last few weeks of announcements >>> being >>> made without any prior list discussion. >>> >>> Please can I remind all members of the Dubbo community that project >>> decisions must be made on list. That typically means: >>> - there is a proposal >>> - there is a discussion >> >> >> One technical question: Some of the contributors may find themselves >> difficult to express their ideas in English. >> Is there some way to help them? What I can think is: >> >> 1. Chinese follows English on the mailing list >> 2. Another Chinese public channel (e.g. gitter) to discuss, and then >> back to mailing list >> 3. Using English anyway >> >> What do you guys think? > > What I have recommended in the past is: > - express the problem as best you can in English (if that is not at all, > that is fine) > - then repeat but using your native language That should go with 1. > > A combination of the above and Google translate is nearly always enough for > someone familiar with the topic to work out what is meant. Make sense to me. > > Once the project decides how it wants to handle this, it needs to be added, > in multiple languages, to the relevant project pages on how to contribute / > participate. +1. Will put that in the discussion thread of the new website. > > Mark > > > >> >>> - the discussion reaches a consensus (rarely, a VOTE is held) >>> - the consensus is announced as a decision of the project >>> >>> Normally, the above steps would take place on the dev@ list. Depending on >>> circumstances, it could also occur in other locations such as the issue >>> tracker. Whereever it does happen, it must be a public forum and the >>> whole >>> community must have an opportunity to contribute to the discussion. >>> >>> Mark >> >> >> >> > -- Best Regards！ Huxing
Re: Project decisions need to be made on list
On 14/06/2018 15:36, Huxing Zhang wrote: On Thu, Jun 14, 2018 at 3:09 PM, Mark Thomas wrote: All, I have seen multiple instances in the last few weeks of announcements being made without any prior list discussion. Please can I remind all members of the Dubbo community that project decisions must be made on list. That typically means: - there is a proposal - there is a discussion One technical question: Some of the contributors may find themselves difficult to express their ideas in English. Is there some way to help them? What I can think is: 1. Chinese follows English on the mailing list 2. Another Chinese public channel (e.g. gitter) to discuss, and then back to mailing list 3. Using English anyway What do you guys think? What I have recommended in the past is: - express the problem as best you can in English (if that is not at all, that is fine) - then repeat but using your native language A combination of the above and Google translate is nearly always enough for someone familiar with the topic to work out what is meant. Once the project decides how it wants to handle this, it needs to be added, in multiple languages, to the relevant project pages on how to contribute / participate. Mark - the discussion reaches a consensus (rarely, a VOTE is held) - the consensus is announced as a decision of the project Normally, the above steps would take place on the dev@ list. Depending on circumstances, it could also occur in other locations such as the issue tracker. Whereever it does happen, it must be a public forum and the whole community must have an opportunity to contribute to the discussion. Mark
?????????????????????????????? header ?????? serialID
Dr All: ?? dubbo ??hessian2go?? https://github.com/alexstocks/go-practice/blob/master/hessian/main.go ?? serialID??031?? serialID [1, 3, 4, 5, 6, 7] ?? 2018-06-14 14:50:04,598 [New I/O server worker #1-1] WARN alibaba.dubbo.rpc.protocol.dubbo.DubboCodec (DubboCodec.java:140) - [DUBBO] Decode request failed: Flag error, expect OBJECT_NULL|OBJECT_DUMMY|OBJECT_DESC|OBJECT_DESC_ID, get 78, dubbo version: 2.5.4, current host: 127.0.0.1 java.io.IOException: Flag error, expect OBJECT_NULL|OBJECT_DUMMY|OBJECT_DESC|OBJECT_DESC_ID, get 78 at com.alibaba.dubbo.common.serialize.support.dubbo.GenericObjectInput.readObject(GenericObjectInput.java:79) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decodeHeartbeatData(ExchangeCodec.java:381) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody(DubboCodec.java:121) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:118) at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:79) at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.decode(DubboCountCodec.java:46) at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:134) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349) at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2018-06-14 14:50:05,599 [New I/O server worker #1-1] WARN com.alibaba.dubbo.remoting.transport.AbstractServer (AbstractServer.java:199) - [DUBBO] All clients has discontected from /127.0.0.1:2. You can graceful shutdown now., dubbo version: 2.5.4, current host: 127.0.0.1 ?? dubbo commiter ?? ID ID https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo-common/src/main/java/com/alibaba/dubbo/common/serialize/support/json/FastJsonSerialization.java?? okay ?? header ?? serialID?? serialID??
Re: Project decisions need to be made on list
On Thu, Jun 14, 2018 at 3:09 PM, Mark Thomas wrote: > All, > > I have seen multiple instances in the last few weeks of announcements being > made without any prior list discussion. > > Please can I remind all members of the Dubbo community that project > decisions must be made on list. That typically means: > - there is a proposal > - there is a discussion One technical question: Some of the contributors may find themselves difficult to express their ideas in English. Is there some way to help them? What I can think is: 1. Chinese follows English on the mailing list 2. Another Chinese public channel (e.g. gitter) to discuss, and then back to mailing list 3. Using English anyway What do you guys think? > - the discussion reaches a consensus (rarely, a VOTE is held) > - the consensus is announced as a decision of the project > > Normally, the above steps would take place on the dev@ list. Depending on > circumstances, it could also occur in other locations such as the issue > tracker. Whereever it does happen, it must be a public forum and the whole > community must have an opportunity to contribute to the discussion. > > Mark -- Best Regards！ Huxing
Assigning Github issues to non-committer user
Hi, I found that I can not assign issue to a non-committer user. If some of the user would like to take an issue, how can I assign to him/her? -- Best Regards！ Huxing
Re: Project decisions need to be made on list
Hi Mark, Thanks for reminding. I think learning the Apache way of how to reach a decisions is one of the most import thing during the incubation process. There might be some mistakes, but the PPMC will try their best to ensure every decision is happened publicly and on the mailing list. On Thu, Jun 14, 2018 at 3:09 PM, Mark Thomas wrote: > All, > > I have seen multiple instances in the last few weeks of announcements being > made without any prior list discussion. > > Please can I remind all members of the Dubbo community that project > decisions must be made on list. That typically means: > - there is a proposal > - there is a discussion > - the discussion reaches a consensus (rarely, a VOTE is held) > - the consensus is announced as a decision of the project > > Normally, the above steps would take place on the dev@ list. Depending on > circumstances, it could also occur in other locations such as the issue > tracker. Whereever it does happen, it must be a public forum and the whole > community must have an opportunity to contribute to the discussion. > > Mark -- Best Regards！ Huxing
Project decisions need to be made on list
All, I have seen multiple instances in the last few weeks of announcements being made without any prior list discussion. Please can I remind all members of the Dubbo community that project decisions must be made on list. That typically means: - there is a proposal - there is a discussion - the discussion reaches a consensus (rarely, a VOTE is held) - the consensus is announced as a decision of the project Normally, the above steps would take place on the dev@ list. Depending on circumstances, it could also occur in other locations such as the issue tracker. Whereever it does happen, it must be a public forum and the whole community must have an opportunity to contribute to the discussion. Mark
