[I] cpu profiler异常符号 (brpc)

2024-10-23 Thread via GitHub
icexin opened a new issue, #2795: URL: https://github.com/apache/brpc/issues/2795 ![image](https://github.com/user-attachments/assets/aa6840ee-e03f-4435-9dd0-ced1056f4c2e) 如图,很多热点最终指向了这个函数,是什么意思? -- This is an automated message from the Apache Git Service. To respond to the message, pl

Oncall report from Oct 14th to Oct 20th

2024-10-23 Thread he lei
hi all: In past week, 2 issues were closed and 4 PR was merged: - https://github.com/apache/brpc/pull/2789 - https://github.com/apache/brpc/pull/2787 - https://github.com/apache/brpc/pull/2778 - https://github.com/apache/brpc/pull/2784 Best regards, he lei lhe...@163.com ---

Re: [VOTE] Release Apache bRPC 1.11.0

2024-10-23 Thread James Ge
+1 binding I've 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. [ ] All files have license headers if necessary. [x] No com

Re: [VOTE] Release Apache bRPC 1.11.0

2024-10-23 Thread Guangming Chen
+1 non-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]

Re: [I] Used the free memory ?? (brpc)

2024-10-23 Thread via GitHub
QiAnXinCodeSafe closed issue #2794: Used the free memory ?? URL: https://github.com/apache/brpc/issues/2794 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-ma

Re: [I] Used the free memory ?? (brpc)

2024-10-23 Thread via GitHub
QiAnXinCodeSafe commented on issue #2794: URL: https://github.com/apache/brpc/issues/2794#issuecomment-2434451863 Thank you for your reply -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the spec