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
