This is an automated oncall report for apache/brpc covering 2026-09-07
to 2026-09-13 (week 2026-W37).

1. Resolved issues

- #3249 【建议】能不能把依赖的那些三方库以submodule的形式添加在git上,要不然还要自己挨个去下载安装 - closed
(https://github.com/apache/brpc/issues/3249)

2. Merged PRs

- #3352 Support end-to-end ECE negotiation in RDMA handshake V3
(https://github.com/apache/brpc/pull/3352)
- #3364 Fix bazel compile error on macOS
(https://github.com/apache/brpc/pull/3364)
- #3444 Refactor NULL with nullptr in butil
(https://github.com/apache/brpc/pull/3444)
- #3493 Limit streams accepted per request
(https://github.com/apache/brpc/pull/3493)
- #3502 Add bounded-load consistent hashing load balancer
(c_murmurhash_bl) (https://github.com/apache/brpc/pull/3502)
- #3517 Replace popen('uname -ap') with uname() syscall in bvar
kernel_version (https://github.com/apache/brpc/pull/3517)
- #3523 Freeze bvar dump path flags and cap pprof duration by
FLAGS_max_profiling_seconds (https://github.com/apache/brpc/pull/3523)
- #3525 Serve builtin services only on ServerOptions.internal_port
(https://github.com/apache/brpc/pull/3525)
- #3527 docs: update web documentation and resource links
(https://github.com/apache/brpc/pull/3527)
- #3531 Fix stream count test cleanup (https://github.com/apache/brpc/pull/3531)
- #3533 Validate Discovery response object fields
(https://github.com/apache/brpc/pull/3533) - note: a CVE is required
for this malformed naming-service reply fix

3. Needs attention

Issues:

- #3528 希望可以修改cmake文件支持conan - needs more info from the reporter
(exact error, Conan and protobuf versions) to decide whether it is a
local configuration issue or a real CMakeLists change is needed
(https://github.com/apache/brpc/issues/3528)
- #3530 Socket health-check/revive 后丢失 client_host 绑定,但仍保留
SO_BINDTODEVICE - confirmed bug with a clear root cause; needs a
developer to pick it up and fix
(https://github.com/apache/brpc/issues/3530)
- #516 h2c/grpc遗留问题 - long-standing leftover issue, awaiting
maintainer triage (https://github.com/apache/brpc/issues/516)

PRs:

- #3428 feat: add URMA transport support - needs a maintainer review
(https://github.com/apache/brpc/pull/3428)
- #3484 Feat: Add adaptive input message batching - new unit tests
access private members/static methods and would fail to compile;
author needs to address this
(https://github.com/apache/brpc/pull/3484)
- #3498 feat: limit Redis server connections - all review comments
addressed, CI still pending; review once CI finishes
(https://github.com/apache/brpc/pull/3498)
- #3507 Add UBRing data format negotiation - logic reviewed and
correct; needs final maintainer approval
(https://github.com/apache/brpc/pull/3507)
- #3516 OSS-Fuzz: Add new fuzzer and corpora targets rtmp - waiting
for the author to respond to review comments
(https://github.com/apache/brpc/pull/3516)
- #3524 Bound the number of http headers and query parameters per
message - review feedback added but author has not pushed new code yet
(https://github.com/apache/brpc/pull/3524)
- #3526 Add cross-scheme slow-start warm-up ramp for newly added
servers - all comments fixed, CI pending; re-review after CI completes
(https://github.com/apache/brpc/pull/3526)
- #3529 Escape HTML output in builtin /flags service - awaiting review
(https://github.com/apache/brpc/pull/3529)
- #3532 Ignore canceled requests in the circuit breaker - change is
minimal and correct; needs maintainer approval
(https://github.com/apache/brpc/pull/3532)
- #3534 refactor(butil): replace integer string conversions - no
functional regression found; CI not fully green yet, follow up on CI
and pending review concerns (https://github.com/apache/brpc/pull/3534)
- #3535 feat: add common transport-level handshake for RDMA and UBSHM
- significant issues confirmed (cross-protocol cast crash, resource
leak on fallback, UBSHM hello out-of-bounds read, phase/EINTR sync);
author needs to fix these (https://github.com/apache/brpc/pull/3535)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to