You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brpc.apache.org by Lorin Lee <lo...@apache.org> on 2021/07/01 13:25:49 UTC
Apache brpc(Incubating) github issue weekly oncall report (
21/06/2021 - 27/06/2021)
Hi all,
Here is the Apache brpc(Incubating) github issue weekly oncall report from
21/06/2021 to 27/06/2021.
This week we resolved 6 issues as below
1. https://github.com/apache/incubator-brpc/issues/1443
2. https://github.com/apache/incubator-brpc/issues/1436
3. https://github.com/apache/incubator-brpc/issues/1437
4. https://github.com/apache/incubator-brpc/issues/1424
5. https://github.com/apache/incubator-brpc/issues/1423
6. https://github.com/apache/incubator-brpc/issues/1416
And there are 4 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1447
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 4 issues that need to have a discussion, to determine if we
should support them or not.
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
SerializedRequest
which makes baidu-std can send any type of data in the request, brpc also
needs to support any type of data in response. Related issue:
https://github.com/apache/incubator-brpc/issues/1444
3. Support customized function to process bvar name. The default
function to_underscored_name may generate some confusing names. Related
issue: https://github.com/apache/incubator-brpc/issues/1445
4. Fix memory leak caused by bthread_setspecific. bthread_setspecific
may new a KeyTable, and return it to KeyTablePool after bthread ends, and
next time it will create a new one again, which makes memory leaked.
Related issues: https://github.com/apache/incubator-brpc/issues/1449
Best regards,
Lorin Lee
Re: Apache brpc(Incubating) github issue weekly oncall report (
28/06/2021 - 04/07/2021)
Posted by Juan Pan <pa...@apache.org>.
Nice job. ;-)
------------------------------------------------------------------------------
Juan Pan(Trista), Apache ShardingSphere PMC
Twitter, @trista86934690
On 07/12/2021 12:07，Jerry Tan<je...@apache.org> wrote：
thanks， daojin。
On 2021/07/08 11:20:10, "caidaojin" <64...@qq.com.INVALID> wrote:
Hi everyone,
Here is the Apache brpc(Incubating) github issue weekly oncall report from 28/06/2021 to 04/07/2021.
This week we resolved 4 issues as below
1. https://github.com/apache/incubator-brpc/issues/1447
2. https://github.com/apache/incubator-brpc/issues/1458
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 3 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1450
3. https://github.com/apache/incubator-brpc/issues/1455
And there are 2 issues that need to have a futher discussion, to determine if we should support them or not.
1. Fix memory leak caused by bthread_setspecific. bthread_setspecific may new a KeyTable, and return it to KeyTablePool after bthread ends, and next time it will create a new one again, which makes memory leaked. Related issues: https://github.com/apache/incubator-brpc/issues/1449
2. Support latest protobuf versions. Related issues: https://github.com/apache/incubator-brpc/issues/1454
Regards,
Daojin
------------------ 原始邮件 ------------------
发件人: "dev" <lo...@apache.org>;
发送时间: 2021年7月1日(星期四) 晚上9:25
收件人: "dev"<de...@brpc.apache.org>;
主题: Apache brpc(Incubating) github issue weekly oncall report ( 21/06/2021 - 27/06/2021)
Hi all,
Here is the Apache brpc(Incubating) github issue weekly oncall report from
21/06/2021 to 27/06/2021.
This week we resolved 6 issues as below
1. https://github.com/apache/incubator-brpc/issues/1443
2. https://github.com/apache/incubator-brpc/issues/1436
3. https://github.com/apache/incubator-brpc/issues/1437
4. https://github.com/apache/incubator-brpc/issues/1424
5. https://github.com/apache/incubator-brpc/issues/1423
6. https://github.com/apache/incubator-brpc/issues/1416
And there are 4 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1447
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 4 issues that need to have a discussion, to determine if we
should support them or not.
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
SerializedRequest
which makes baidu-std can send any type of data in the request, brpc also
needs to support any type of data in response. Related issue:
https://github.com/apache/incubator-brpc/issues/1444
3. Support customized function to process bvar name. The default
function to_underscored_name may generate some confusing names. Related
issue: https://github.com/apache/incubator-brpc/issues/1445
4. Fix memory leak caused by bthread_setspecific. bthread_setspecific
may new a KeyTable, and return it to KeyTablePool after bthread ends, and
next time it will create a new one again, which makes memory leaked.
Related issues: https://github.com/apache/incubator-brpc/issues/1449
Best regards,
Lorin Lee
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Re: Apache brpc(Incubating) github issue weekly oncall report ( 28/06/2021 - 04/07/2021)
Posted by Jerry Tan <je...@apache.org>.
thanks， daojin。
On 2021/07/08 11:20:10, "caidaojin" <64...@qq.com.INVALID> wrote:
> Hi everyone,
>
>
> Here is the Apache brpc(Incubating) github issue weekly oncall report from 28/06/2021 to 04/07/2021.
>
>
> This week we resolved 4 issues as below
> 1. https://github.com/apache/incubator-brpc/issues/1447
> 2. https://github.com/apache/incubator-brpc/issues/1458
> 3. https://github.com/apache/incubator-brpc/issues/1441
> 4. https://github.com/apache/incubator-brpc/issues/1438
>
>
> And there are 3 issues that still need to follow up
> 1. https://github.com/apache/incubator-brpc/issues/1448
> 2. https://github.com/apache/incubator-brpc/issues/1450
> 3. https://github.com/apache/incubator-brpc/issues/1455
>
>
> And there are 2 issues that need to have a futher discussion, to determine if we should support them or not.
>
>
> 1. Fix memory leak caused by bthread_setspecific. bthread_setspecific may new a KeyTable, and return it to KeyTablePool after bthread ends, and next time it will create a new one again, which makes memory leaked. Related issues: https://github.com/apache/incubator-brpc/issues/1449
>
>
> 2. Support latest protobuf versions. Related issues: https://github.com/apache/incubator-brpc/issues/1454
>
>
> Regards,
>
>
> Daojin
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "dev" <lo...@apache.org>;
> 发送时间: 2021年7月1日(星期四) 晚上9:25
> 收件人: "dev"<de...@brpc.apache.org>;
>
> 主题: Apache brpc(Incubating) github issue weekly oncall report ( 21/06/2021 - 27/06/2021)
>
>
>
> Hi all,
>
>
>
> Here is the Apache brpc(Incubating) github issue weekly oncall report from
> 21/06/2021 to 27/06/2021.
>
>
>
> This week we resolved 6 issues as below
>
> 1. https://github.com/apache/incubator-brpc/issues/1443
> 2. https://github.com/apache/incubator-brpc/issues/1436
> 3. https://github.com/apache/incubator-brpc/issues/1437
> 4. https://github.com/apache/incubator-brpc/issues/1424
> 5. https://github.com/apache/incubator-brpc/issues/1423
> 6. https://github.com/apache/incubator-brpc/issues/1416
>
>
>
> And there are 4 issues that still need to follow up
>
> 1. https://github.com/apache/incubator-brpc/issues/1448
> 2. https://github.com/apache/incubator-brpc/issues/1447
> 3. https://github.com/apache/incubator-brpc/issues/1441
> 4. https://github.com/apache/incubator-brpc/issues/1438
>
>
>
> And there are 4 issues that need to have a discussion, to determine if we
> should support them or not.
>
> 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
> SerializedRequest
> which makes baidu-std can send any type of data in the request, brpc also
> needs to support any type of data in response. Related issue:
> https://github.com/apache/incubator-brpc/issues/1444
> 3. Support customized function to process bvar name. The default
> function to_underscored_name may generate some confusing names. Related
> issue: https://github.com/apache/incubator-brpc/issues/1445
> 4. Fix memory leak caused by bthread_setspecific. bthread_setspecific
> may new a KeyTable, and return it to KeyTablePool after bthread ends, and
> next time it will create a new one again, which makes memory leaked.
> Related issues: https://github.com/apache/incubator-brpc/issues/1449
>
>
>
> Best regards,
>
>
> Lorin Lee
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org
Apache brpc(Incubating) github issue weekly oncall report ( 28/06/2021 - 04/07/2021)
Posted by caidaojin <64...@qq.com.INVALID>.
Hi everyone,
Here is the Apache brpc(Incubating) github issue weekly oncall report from 28/06/2021 to 04/07/2021.
This week we resolved 4 issues as below
1. https://github.com/apache/incubator-brpc/issues/1447
2. https://github.com/apache/incubator-brpc/issues/1458
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 3 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1450
3. https://github.com/apache/incubator-brpc/issues/1455
And there are 2 issues that need to have a futher discussion, to determine if we should support them or not.
1. Fix memory leak caused by bthread_setspecific. bthread_setspecific may new a KeyTable, and return it to KeyTablePool after bthread ends, and next time it will create a new one again, which makes memory leaked. Related issues: https://github.com/apache/incubator-brpc/issues/1449
2. Support latest protobuf versions. Related issues: https://github.com/apache/incubator-brpc/issues/1454
Regards,
Daojin
------------------ 原始邮件 ------------------
发件人: "dev" <lorinlee@apache.org>;
发送时间: 2021年7月1日(星期四) 晚上9:25
收件人: "dev"<dev@brpc.apache.org>;
主题: Apache brpc(Incubating) github issue weekly oncall report ( 21/06/2021 - 27/06/2021)
Hi all,
Here is the Apache brpc(Incubating) github issue weekly oncall report from
21/06/2021 to 27/06/2021.
This week we resolved 6 issues as below
1. https://github.com/apache/incubator-brpc/issues/1443
2. https://github.com/apache/incubator-brpc/issues/1436
3. https://github.com/apache/incubator-brpc/issues/1437
4. https://github.com/apache/incubator-brpc/issues/1424
5. https://github.com/apache/incubator-brpc/issues/1423
6. https://github.com/apache/incubator-brpc/issues/1416
And there are 4 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1447
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 4 issues that need to have a discussion, to determine if we
should support them or not.
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
SerializedRequest
which makes baidu-std can send any type of data in the request, brpc also
needs to support any type of data in response. Related issue:
https://github.com/apache/incubator-brpc/issues/1444
3. Support customized function to process bvar name. The default
function to_underscored_name may generate some confusing names. Related
issue: https://github.com/apache/incubator-brpc/issues/1445
4. Fix memory leak caused by bthread_setspecific. bthread_setspecific
may new a KeyTable, and return it to KeyTablePool after bthread ends, and
next time it will create a new one again, which makes memory leaked.
Related issues: https://github.com/apache/incubator-brpc/issues/1449
Best regards,
Lorin Lee
Re: Apache brpc(Incubating) github issue weekly oncall report (
21/06/2021 - 27/06/2021)
Posted by 谭中意 <zh...@gmail.com>.
thanks， weibing。
On Fri, Jul 2, 2021 at 10:15 AM Wang,Weibing <wa...@baidu.com> wrote:
> 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
> SerializedRequest
> which makes baidu-std can send any type of data in the request,
> brpc also
> needs to support any type of data in response. Related issue:
> https://github.com/apache/incubator-brpc/issues/1444
> 3. Support customized function to process bvar name. The default
> function to_underscored_name may generate some confusing names.
> Related
> issue: https://github.com/apache/incubator-brpc/issues/1445
>
> We have already solved these three issues inside Baidu. We will submit
> these PRs later.
>
>
> Thanks
> Weibing Wang
>
> 在 2021/7/1 下午9:26，“Lorin Lee”<lo...@apache.org> 写入:
>
> Hi all,
>
>
>
> Here is the Apache brpc(Incubating) github issue weekly oncall report
> from
> 21/06/2021 to 27/06/2021.
>
>
>
> This week we resolved 6 issues as below
>
> 1. https://github.com/apache/incubator-brpc/issues/1443
> 2. https://github.com/apache/incubator-brpc/issues/1436
> 3. https://github.com/apache/incubator-brpc/issues/1437
> 4. https://github.com/apache/incubator-brpc/issues/1424
> 5. https://github.com/apache/incubator-brpc/issues/1423
> 6. https://github.com/apache/incubator-brpc/issues/1416
>
>
>
> And there are 4 issues that still need to follow up
>
> 1. https://github.com/apache/incubator-brpc/issues/1448
> 2. https://github.com/apache/incubator-brpc/issues/1447
> 3. https://github.com/apache/incubator-brpc/issues/1441
> 4. https://github.com/apache/incubator-brpc/issues/1438
>
>
>
> And there are 4 issues that need to have a discussion, to determine if
> we
> should support them or not.
>
> 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
> SerializedRequest
> which makes baidu-std can send any type of data in the request,
> brpc also
> needs to support any type of data in response. Related issue:
> https://github.com/apache/incubator-brpc/issues/1444
> 3. Support customized function to process bvar name. The default
> function to_underscored_name may generate some confusing names.
> Related
> issue: https://github.com/apache/incubator-brpc/issues/1445
> 4. Fix memory leak caused by bthread_setspecific.
> bthread_setspecific
> may new a KeyTable, and return it to KeyTablePool after bthread
> ends, and
> next time it will create a new one again, which makes memory leaked.
> Related issues:
> https://github.com/apache/incubator-brpc/issues/1449
>
>
>
> Best regards,
>
>
> Lorin Lee
>
>
>
Re: Apache brpc(Incubating) github issue weekly oncall report (
21/06/2021 - 27/06/2021)
Posted by "Wang,Weibing" <wa...@baidu.com>.
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
SerializedRequest
which makes baidu-std can send any type of data in the request, brpc also
needs to support any type of data in response. Related issue:
https://github.com/apache/incubator-brpc/issues/1444
3. Support customized function to process bvar name. The default
function to_underscored_name may generate some confusing names. Related
issue: https://github.com/apache/incubator-brpc/issues/1445
We have already solved these three issues inside Baidu. We will submit these PRs later.
Thanks
Weibing Wang
在 2021/7/1 下午9:26，“Lorin Lee”<lo...@apache.org> 写入:
Hi all,
Here is the Apache brpc(Incubating) github issue weekly oncall report from
21/06/2021 to 27/06/2021.
This week we resolved 6 issues as below
1. https://github.com/apache/incubator-brpc/issues/1443
2. https://github.com/apache/incubator-brpc/issues/1436
3. https://github.com/apache/incubator-brpc/issues/1437
4. https://github.com/apache/incubator-brpc/issues/1424
5. https://github.com/apache/incubator-brpc/issues/1423
6. https://github.com/apache/incubator-brpc/issues/1416
And there are 4 issues that still need to follow up
1. https://github.com/apache/incubator-brpc/issues/1448
2. https://github.com/apache/incubator-brpc/issues/1447
3. https://github.com/apache/incubator-brpc/issues/1441
4. https://github.com/apache/incubator-brpc/issues/1438
And there are 4 issues that need to have a discussion, to determine if we
should support them or not.
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
SerializedRequest
which makes baidu-std can send any type of data in the request, brpc also
needs to support any type of data in response. Related issue:
https://github.com/apache/incubator-brpc/issues/1444
3. Support customized function to process bvar name. The default
function to_underscored_name may generate some confusing names. Related
issue: https://github.com/apache/incubator-brpc/issues/1445
4. Fix memory leak caused by bthread_setspecific. bthread_setspecific
may new a KeyTable, and return it to KeyTablePool after bthread ends, and
next time it will create a new one again, which makes memory leaked.
Related issues: https://github.com/apache/incubator-brpc/issues/1449
Best regards,
Lorin Lee