Re: hi,guys,if you have subscribed this mail list,please reply with +1

2019-01-01 Thread Wang,Weibing
+1 Weibing Wang 在 2018/12/21 11:46,“朱佳顺” 写入: +1 Kevin A. McGrail 于2018年12月20日 周四22:20写道: > +1 > > On 12/20/2018 3:44 AM, Tan,Zhongyi wrote: > > So we can know that you are here already. > > > > Thanks > > > > -- > Kevin A. McGrail >

Re: the tasklist that needed for the first apache release

2019-03-28 Thread Wang,Weibing
I would like to take 3. 在 2019/3/28 09:23,“tan zhongyi” 写入: Thanks,zhangyi, Anyone else who want to volunteer to take some task? 在 2019/3/27 下午10:17,“Zhangyi Chen” 写入: I would like take 1 and 2. On Tue, Mar 26, 2019 at 2:25 PM tan zhongyi wro

Re: the tasklist that needed for the first apache release

2019-04-10 Thread Wang,Weibing
ll source files, including .h, .cpp, .java, etc @wang weibing Hi, weibing, would you please make a short license header for us to review first? thanks 4. Check the source tarball to make sure it does not contain binary files except for data @TanZhongy

Re: Update for tasklist that needed for the first apache release and target timeline

2019-06-28 Thread Wang,Weibing
2. Make a short License Header and add to all source code @Wang,Weibing This is done. Thanks. 在 2019/6/19 12:35,“tan zhongyi” 写入: Hi, all, Please update your working status by reply this email, Thanks It seems that jiashun has got big

Re: Apache brpc(Incubating) github issue weekly oncall report ( 21/06/2021 - 27/06/2021)

2021-07-01 Thread Wang,Weibing
1. Support passes the client's timeout to the server and the server can get the client's timeout by calling Controller::timeout_us(). Related issue: https://github.com/apache/incubator-brpc/issues/1440 2. Support any type of data in baidu-std's response. Just like Se

Oncall report from Jan 24th to Feb 6th

2022-02-07 Thread Wang,Weibing
Hi all During the last two weeks 7 issues were closed and 2 PRs were merged: https://github.com/apache/incubator-brpc/pull/1651 https://github.com/apache/incubator-brpc/pull/1677 And these PRs look good to me, but it's better to be double checked by another committer: https://github.com/apache/

Re: hello brpc

2022-03-10 Thread Wang,Weibing
Welcome ! > > > 在 2022/3/1 下午2:27,“tan zhongyi” 写入: > > Welcome > > > 发件人: 刘帅 > 日期: 星期二, 2022年3月1日 下午2:23 > 收件人: dev@brpc.apache.org > 主题: hello brpc > Hi all, > > I'm Liu Shuai, from cloud native team of Baidu Infrastructure > Department, > Now I am mainly respo

Oncall report from Mar 7 to Mar 13

2022-03-14 Thread Wang,Weibing
Hi all During the last two weeks 6 issues were closed and 4 PRs were merged: https://github.com/apache/incubator-brpc/pull/1646 https://github.com/apache/incubator-brpc/pull/1468 https://github.com/apache/incubator-brpc/pull/1461 https://github.com/apache/incubator-brpc/pull/1400 Thanks Weibing

bRPC 1.1.0 release plan

2022-03-14 Thread Wang,Weibing
Hi, all After discussing with Zhongyi, I plan to release version 1.1.0 from the current master branch. The current master branch has 106 commits after 1.0.0: https://github.com/apache/incubator-brpc/compare/1.0.0...master Most of the commits are bug fixes or document improvements. Some are new fea

Re: Vote to accept Liu Shuai as a committer

2022-03-16 Thread Wang,Weibing
+1 On Thu, Mar 17, 2022 at 9:51 AM Wang Wei wrote: > +1 > > On Thu, Mar 17, 2022 at 8:47 AM tan zhongyi wrote: > > > Vote to accept Liu Shuai as a committer > > > > > > > > Hi, guys, > > > > > > > > Time to vote now, > > > > I would like to call for vote to accept Liu Shuai as a committer to ou

Re: Vote to accept Liu Shuai as a committer

2022-03-22 Thread Wang,Weibing
Congratulations! On Tue, Mar 22, 2022 at 2:53 PM Jerry Tan wrote: > let me count . > > we have Wangwei, lhestz, wangweibing, jerrytan, lorinlee, fisherman, > caidaojin, > 7 +1 , > no -1, and no 0. > > I will close it as passed. > > On 2022/03/20 03:00:52 fisherman wrote: > > +1 > > > > Lorin L

Re: bRPC 1.1.0 release plan

2022-03-24 Thread Wang,Weibing
hongyi wrote: > It is the first time for Wang Weibing to be responsible for release, > Thanks for lorin’s document, he will reference it carefully. > > Please be patient for him. > > And If there is any problem, please help him, > Thanks. > > 发件人: Wang,Weibing >

Re: bRPC 1.1.0 release plan

2022-03-28 Thread Wang,Weibing
/github.com/apache/incubator-brpc/pull/1567> And I will start to release version 1.1.0 this week following this guide: https://github.com/apache/incubator-brpc/blob/master/community/release_cn.md Thanks Weibing On Fri, Mar 25, 2022 at 12:32 PM Wang,Weibing wrote: > Remind, If there ar

[VOTE] Release Apache brpc (Incubating) 1.1.0

2022-03-29 Thread Wang,Weibing
Hello Apache brpc (Incubating) Community, This is a call for vote to release Apache brpc (Incubating) version 1.1.0 [Release Note] - Support ipv6 and unix domain socket by @wwbmmm in #1560 - Support protobuf 3.19.x by @hcoona in #1679 - Support http protocol dump and replay by @guodongxi

[Result] [VOTE] Release Apache brpc (Incubating) 1.1.0

2022-04-01 Thread Wang,Weibing
Hi all, The vote to release Apache brpc (Incubating) 1.1.0 has passed. The vote PASSED with 6 binding +1, 0 non binding +1 and 0 -1 votes: Binding votes: - Wang Wei - Jiashun Zhu - James Ge - Yao Wang - Shuai Liu - Juan Pan Vote thread: https://lists.apache.org/thread/6p

[ANNOUNCE] Apache brpc 1.1.0

2022-04-11 Thread Wang,Weibing
Hi all, The Apache brpc (incubating) community is pleased to announce that Apache brpc (incubating) 1.1.0 has been released! brpc is an industrial-grade RPC framework with extremely high performance, and it supports multiple protocols, full rpc features, and has many convenient tools. Brief note

Re: Meeting minutes of committer's meeting on June 1st

2022-06-05 Thread Wang,Weibing
committer meeting. > > We have Ge Jun, Zhu jiashun, Wang Weibing, Liu shuai, Hu Xiguo, Wang Wei, > Tan zhongyi, Pan Juan, Li Lei joined the meeting, > And discussed the status of the project and members. > > Here is todo list: > > > 1. Release a new version by July (@

Re: Say hello to bRPC community

2022-06-05 Thread Wang Weibing
Welcome! Xiguo has done a lot for the bRPC website. And he developed the graceful restart feature for bRPC inside Baidu. I hope this feature can be opensource soon. Thanks! Weibing On 2022/06/04 07:52:50 Hu go wrote: > Hi, all: > > I'm Xiguo Hu, from the Cloud Native Team of Baidu Infrastructu

Re: about apachecon asia 2022 rpc forum

2022-08-02 Thread Wang,Weibing
Tan wrote: > > Hi, guys, > > nice to announce that > > we have finished apachecon asia 2022 rpc forum. > > > > this time, we organized one separate forum focused on RPC framework, > > and we work together with Apache Dubbo guys. > > Wang Weibing is the co-chai

Re: meeting minutes for today‘s dinner meeting with Panjuan

2022-08-04 Thread Wang,Weibing
> > > > we have dinner with our mentor Panjuan tonight, > > the attendee includes Wang Weibing, Liu Shuai, Hu Xiguo, Wang Xiaofeng, > Li > > Lei, Tan zhongyi and PanJuan. > > > > PanJuan gave us two pieces of advice: >

Re: meeting minutes for today‘s dinner meeting with Panjuan

2022-08-04 Thread Wang,Weibing
more users and > developers, and so grow the community. > > Regards > JB > > On Thu, Aug 4, 2022 at 4:42 PM Jerry Tan wrote: > > > > Hi, guys, > > > > we have dinner with our mentor Panjuan tonight, > > the attendee includes Wang Weibing, Liu Shua

Re: Oncall report from Aug 1st to 7th

2022-08-11 Thread Wang,Weibing
Good. Since Daojin, Gaidong and Me have reviewed this PR, if there are no more comments after this week, I will merge it. Best Regards Weibing On Wed, Aug 10, 2022 at 7:52 PM caidaojin <642580...@qq.com.invalid> wrote: > > Hi,  > > Closed some issues. And I reviewed following two MRs: > https://g

Re: [NEW FEATURES] Apache brpc bvar WindowEx and PerSecondEx feature available

2022-08-23 Thread Wang,Weibing
Good job! On Tue, Aug 23, 2022 at 7:21 PM Shuai Liu wrote: > > Hi all, > > I am pleased to announce that bvar::WindowEx and bvar::PerSecondEx feature > has been available! > > bvar is high performance counters in multi-threaded applications and view > miscellaneousstatistics > conveniently in mul

Re: [WELCOME] new user JOYY

2022-08-24 Thread Wang,Weibing
Yes, I have contacted chenBright and he is willing to contribute more. Best regards Weibing On Wed, Aug 24, 2022 at 9:07 PM Jerry Tan wrote: > > great > > we can attract some engineers from JOYY to become our contributor。 > > > On 2022/08/24 11:07:08 Shuai Liu wrote: > > Hi all, > > > > Welcome

Re: Please help to review the pod report,thanks

2022-08-30 Thread Wang,Weibing
Looks good to me On Wed, Aug 31, 2022 at 9:37 AM Jerry Tan wrote: > > thanks, I will fix it. > > On 2022/08/30 03:04:55 Shuai Liu wrote: > > we particpated in ApacheCon Asia 2022, PPMC Wang Weibing was the co-chair > > of the RPC tracke. > > > > RPC track

Re: Hi, what is the status for the RDMA patch?

2022-09-13 Thread Wang,Weibing
The RDMA PR(https://github.com/apache/incubator-brpc/pull/1836) has passed code review by Jiashun and me. Since it has slight difference with Baidu internal version on production, Zhaogeng plan to push this new version to production this month. If it has no problem on production, I will then merge

Re: Hi, what is the status for the RDMA patch?

2022-09-13 Thread Wang,Weibing
Not necessarily, it depends on the progress of the production deployment. Best regards Weibing On Wed, Sep 14, 2022 at 10:55 AM Jerry Tan wrote: > > so hopefully, it will be merged into trunk by the end of this month? > > > On 2022/09/14 02:18:01 "Wang,Weibing" wro

Re: status of branding name register

2022-09-15 Thread Wang,Weibing
Congratulations! On Fri, Sep 16, 2022 at 8:43 AM Jerry Tan wrote: > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-202 > > Mark Thomas, the VP of Apache Brand Management, > > has updated the issue as > > ”Name approved.“ > > it means that ASF has accepted the branding name and will reg

Re: Hello to the bRPC community

2022-10-09 Thread Wang,Weibing
Welcome! On Mon, Oct 10, 2022 at 10:24 AM 陈光明 wrote: > > Hey guys, > > I'm Guangming Chen, from the yy company, mainly responsible for developing > and maintaining C++ microservice based on bRPC framework. > > My GitHUb address is https://github.com/chenBright . Here are my > contributions: > >

Re: [VOTE] Release Apache brpc (Incubating) 1.3.0

2022-10-13 Thread Wang Weibing
+1 (binding) I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] All files have license headers if necessary. [x] No compiled archives bundled in source archive. Best regards,

Re: [DISCUSS] Graduate Apache brpc (incubating) as a TLP

2022-10-26 Thread Wang,Weibing
raduation. > > > > > > > > > > if we all agree, I will call for a vote for the graduate. > > > > > > > > > > > > > > > Updates since incubation: > > > > > > > > > > > > > > > 1. We re

Re: [DISCUSS] Graduate Apache brpc (incubating) as a TLP

2022-10-26 Thread Wang,Weibing
will call for a vote for the graduate. > > > Updates since incubation: > > > 1. We release 0.9.6, 0.9.7, 1.0.0,1.1.0, 1.2.0, 1.3.0, 6 releases by > different release managers (including Jerry Tan, Zhu Jiashun, Lorin Lee, > Wang Weibing, Liu Shuai, Hu Xiguo) (see it at &

Re: About explicitly listing all third-part licensed files

2022-10-30 Thread Wang,Weibing
I think we can use `*` to simplify the file list, that will not cause ambiguity. Like attachment `bsd.txt`. Best regards Weibing On Mon, Oct 31, 2022 at 2:38 PM Xiaofeng wrote: > > Hi Trista and the community, > > During the release of 1.3.0, Trista suggested [1] explicitly listing > all the fil

Re: use bRPC as the project name

2022-10-31 Thread Wang,Weibing
I agree. Best regards Weibing On Mon, Oct 31, 2022 at 11:52 PM Jerry Tan wrote: > > It is recommended to use bRPC uniformly in case-sensitive situations, such > as various documents; > > brpc can be used for insensitive occasions, such as domain name and > official website brpc.apache.org > > do

Re: [VOTE] Release Apache bRPC 1.4.0

2023-01-28 Thread Wang,Weibing
+1 (binding) I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] N

Re: [VOTE] Release Apache bRPC 1.4.0

2023-01-29 Thread Wang,Weibing
> OK, besides these, is there anything else that needs highlight? #1958, #1990, #2041, #2057 these are also new features. Best regards Weibing On Sun, Jan 29, 2023 at 2:24 PM Wang Xiaofeng wrote: > > Hi, > > On 2023/01/29 05:54:35 "Wang,Weibing" wrote: > > +1 (

CVE-2023-31039: Apache bRPC: ServerOptions.pid_file may cause arbitrary code execution

2023-05-07 Thread Wang Weibing
Severity: important Affected versions: - Apache bRPC 0.9.0 before 1.5.0 Description: Security vulnerability in Apache bRPC <1.5.0 on all platforms allows attackers to execute arbitrary code via ServerOptions::pid_file. An attacker that can influence the ServerOptions pid_file parameter with wh

Re: [VOTE] Release Apache bRPC 1.6.0

2023-07-25 Thread Wang,Weibing
+ 1 (binding) I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] N

CVE-2023-45757: Apache bRPC: The builtin service rpcz page has an XSS attack vulnerability

2023-10-15 Thread Wang Weibing
Severity: important Affected versions: - Apache bRPC 0.9.0 through 1.6.0 Description: Security vulnerability in Apache bRPC <=1.6.0 on all platforms allows attackers to inject XSS code to the builtin rpcz page. An attacker that can send http request to bRPC server with rpcz enabled can  inject

Re: [VOTE] Release Apache bRPC 1.8.0

2024-02-01 Thread Wang Weibing
+1 (binding) I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] N

CVE-2024-23452: Apache bRPC: HTTP request smuggling vulnerability

2024-02-07 Thread Wang Weibing
Severity: moderate Affected versions: - Apache bRPC 0.9.5 before 1.8.0 Description: Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request. Vulnerability Cause Description: The http_parser does not comply with the RFC-732

Re: hello brpc

2024-03-10 Thread Wang,Weibing
Welcome! Best regards Weibing Wang On Wed, Mar 6, 2024 at 12:10 PM Wang Xiaofeng wrote: > > Welcome, Liming~ > > Regards, > Xiaofeng > > On 2024/03/06 02:35:33 yangliming wrote: > > Hi all, > > > > I'm Yang Liming, from storage technology center of Meituan Infrastructure > > Department, Now I a

Re: [VOTE] Release Apache bRPC 1.9.0

2024-04-23 Thread Wang,Weibing
+1 binding I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] No

Re: [VOTE] Release Apache bRPC 1.11.0

2024-10-21 Thread Wang,Weibing
+1 binding I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] No

Re: [DISCUSS] Always using English for development, and optionally supporting dedicated Chinese user discussion

2025-04-21 Thread Wang,Weibing
Hello, tison Thanks for your advice! I have created an iss...@brpc.apache.org list and redirect the issue notifications to this list following your instructions. PR notifications will still redirect to the dev@ list. And we will keep PR discussions in English. Best regards Weibing Wang On Mon, A

Re: [VOTE] Release Apache bRPC 1.14.0

2025-07-23 Thread Wang,Weibing
+1 binding I have checked: [x] Download links are valid. [x] Checksums and PGP signatures are valid. [x] Source code distributions have correct names matching the current release. [x] LICENSE and NOTICE files are correct for each brpc repo. [x] All files have license headers if necessary. [x] No