issues  

Messages by Thread

• [I] 多bthread tag下创建socket有可能造成_io_event异常 (brpc) via GitHub
  • Re: [I] 多bthread tag下创建socket有可能造成_io_event异常 (brpc) via GitHub
  • Re: [I] 多bthread tag下创建socket有可能造成_io_event异常 (brpc) via GitHub
  • Re: [I] 多bthread tag下创建socket有可能造成_io_event异常 (brpc) via GitHub
• [I] Support mips54 (brpc) via GitHub
• [I] TimerThread 没有正常初始卡在butil::PlatformThread::SetName("brpc_timer") (brpc) via GitHub
• [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
  • Re: [I] brpc支持GPU Direct RDMA (brpc) via GitHub
• [I] 升级到1.10.0版本后，ServerOptions中的num_threads设置失效了 (brpc) via GitHub
  • Re: [I] 升级到1.10.0版本后，ServerOptions中的num_threads设置失效了 (brpc) via GitHub
  • Re: [I] 升级到1.10.0版本后，ServerOptions中的num_threads设置失效了 (brpc) via GitHub
  • Re: [I] 升级到1.10.0版本后，ServerOptions中的num_threads设置失效了 (brpc) via GitHub
  • Re: [I] 升级到1.10.0版本后，ServerOptions中的num_threads设置失效了 (brpc) via GitHub
• [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
  • Re: [D] Workflow changes when new feature is added [brpc] via GitHub
• Re: [I] 用户注册的bthread local变量析构函数触发bthread切换引起coredump (brpc) via GitHub
• [I] openssl短连接方式访问服务，偶发E1008超时错误 (brpc) via GitHub
• [I] bRPC是否考虑支持证书热加载 (brpc) via GitHub
  • Re: [I] bRPC是否考虑支持证书热加载 (brpc) via GitHub
• [I] 请教一个问题，不适用Protobuf, 直接使用TcpRawService (brpc) via GitHub
  • Re: [I] 请教一个问题，不适用Protobuf, 直接使用TcpRawService (brpc) via GitHub
  • Re: [I] 请教一个问题，不适用Protobuf, 直接使用TcpRawService (brpc) via GitHub
• Re: [I] 进程退出的时候出现了bvar的crash。 (brpc) via GitHub
• [I] core on memory align for SIMD (brpc) via GitHub
  • Re: [I] core on memory align for SIMD (brpc) via GitHub
• [I] 求助：aarch64 下编译失败 (brpc) via GitHub
• [I] brpc coredump 在SendRpcResponse 中的 iobuf clear 中 (brpc) via GitHub
• Re: [I] 用户态tcp实现是否会开源呢？ (brpc) via GitHub
• [I] Support to check all living bthread to help debug (brpc) via GitHub
  • Re: [I] Support to check all living bthread to help debug (brpc) via GitHub
• Re: [I] bthread_id_unlock 失败 “Invalid bthread_id=” (brpc) via GitHub
  • Re: [I] bthread_id_unlock 失败 “Invalid bthread_id=” (brpc) via GitHub
• [I] bthread_id_unlock 失败 (brpc) via GitHub
  • Re: [I] bthread_id_unlock 失败 (brpc) via GitHub
• [I] brpc Server开启mtls验证之后可以通过http端口访问 (brpc) via GitHub
  • Re: [I] brpc Server开启mtls验证之后可以通过http端口访问 (brpc) via GitHub
  • Re: [I] brpc Server开启mtls验证之后可以通过http端口访问 (brpc) via GitHub
  • Re: [I] brpc Server开启mtls验证之后可以通过http端口访问 (brpc) via GitHub
• [I] 请教一个问题，为什么建连的时候connect_abstime会是connect timeout和controller timeout的min值 (brpc) via GitHub
• [I] brpc 没向用户暴露 RPC 从 socket 读取的时间， 我们应该暴露这个信息 (brpc) via GitHub
  • Re: [I] brpc 没向用户暴露 RPC 从 socket 读取的时间， 我们应该暴露这个信息 (brpc) via GitHub
  • Re: [I] brpc 没向用户暴露 RPC 从 socket 读取的时间， 我们应该暴露这个信息 (brpc) via GitHub
  • Re: [I] brpc 没向用户暴露 RPC 从 socket 读取的时间， 我们应该暴露这个信息 (brpc) via GitHub
• [I] flatmap operator= 导致死锁 (brpc) via GitHub
  • Re: [I] flatmap operator= 导致死锁 (brpc) via GitHub
  • Re: [I] flatmap operator= 导致死锁 (brpc) via GitHub
  • Re: [I] flatmap operator= 导致死锁 (brpc) via GitHub
• [I] mvar clear_stats不是线程安全的 (brpc) via GitHub
  • Re: [I] mvar clear_stats不是线程安全的 (brpc) via GitHub
• [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
  • Re: [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
  • Re: [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
  • Re: [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
  • Re: [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
  • Re: [I] span.cpp中destroy()方法存在内存重复释放问题，会导致服务崩掉 (brpc) via GitHub
• [I] 请问brpc支持多个客户端分别创建流和客户端通信么？ (brpc) via GitHub
  • Re: [I] 请问brpc支持多个客户端分别创建流和客户端通信么？ (brpc) via GitHub
  • Re: [I] 请问brpc支持多个客户端分别创建流和客户端通信么？ (brpc) via GitHub
• Re: [I] WSL2-Ubuntu20.04 下运行示例 echo_c++ 结果段错误 (brpc) via GitHub
• [I] bvar IntRecorder引起segfault (brpc) via GitHub
  • Re: [I] bvar IntRecorder引起segfault (brpc) via GitHub
• [I] multiple definition of `InstallSymbolizeOpenObjectFileCallback` when linking with glog (brpc) via GitHub
  • Re: [I] multiple definition of `InstallSymbolizeOpenObjectFileCallback` when linking with glog (brpc) via GitHub
• [I] brpc socket极端场景下修改完version但是没有启动health check，导致socket无法建立新连接 (brpc) via GitHub
  • Re: [I] brpc socket极端场景下修改完version但是没有启动health check，导致socket无法建立新连接 (brpc) via GitHub
  • Re: [I] brpc socket极端场景下修改完version但是没有启动health check，导致socket无法建立新连接 (brpc) via GitHub
• [I] Is it possible to first decide which socket to use for RPC, then serialize the request? (brpc) via GitHub
  • Re: [I] Is it possible to first decide which socket to use for RPC, then serialize the request? (brpc) via GitHub
• [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
  • Re: [I] 请教关于线程阻塞的问题 (brpc) via GitHub
• Re: [I] 紧急求助：报错 symbol lookup error: /usr/local/lib/libbrpc.so: undefined symbol: pthread_mutex_lock (brpc) via GitHub
  • Re: [I] 紧急求助：报错 symbol lookup error: /usr/local/lib/libbrpc.so: undefined symbol: pthread_mutex_lock (brpc) via GitHub
• [I] brpc静态链接的so库，可执行程序调用没有问题，别的so调用会出现googleutexLock::MutexLock崩溃 (brpc) via GitHub
• Re: [I] 多次调用能使server用同一个线程处理么？ (brpc) via GitHub
  • Re: [I] 多次调用能使server用同一个线程处理么？ (brpc) via GitHub
  • Re: [I] 多次调用能使server用同一个线程处理么？ (brpc) via GitHub
  • Re: [I] 多次调用能使server用同一个线程处理么？ (brpc) via GitHub
• Re: [I] bthread在持有了pthread的锁之后，如果遇到bthread_sleep的调用，是否会切换工作线程？？ (brpc) via GitHub
• Re: [I] 看到戈神回复中，切换bthread和切换pthread都是3us左右，为什么bthread还有存在的必要呢 (brpc) via GitHub
• [I] 【高优】bthread::RWLock在写者持有锁期间，读者try_lock_for锁超时失败，会导致读者计数错误 (brpc) via GitHub
• [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
  • Re: [I] Is CRC validation for attachments under consideration? (brpc) via GitHub
• Re: [I] bthread支持多个线程池 (brpc) via GitHub
• Re: [I] brpc只能使用protobuf吗？如果我想使用flatbuffer，能支持吗 (brpc) via GitHub
• [I] brpc stream考虑控制流和数据流分开吗 (brpc) via GitHub
• [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
  • Re: [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
  • Re: [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
  • Re: [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
  • Re: [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
  • Re: [I] 压测 brpc server 过程中出现部分服务卡死 (brpc) via GitHub
• [I] Signal Trace mode may send SIGURG to wrong thread (brpc) via GitHub
  • Re: [I] Signal Trace mode may send SIGURG to wrong thread (brpc) via GitHub
  • Re: [I] Signal Trace mode may send SIGURG to wrong thread (brpc) via GitHub
• Re: [I] brpc RDMA 交互 hello message 失败 (brpc) via GitHub
  • Re: [I] brpc RDMA 交互 hello message 失败 (brpc) via GitHub
  • Re: [I] brpc RDMA 交互 hello message 失败 (brpc) via GitHub
  • Re: [I] brpc RDMA 交互 hello message 失败 (brpc) via GitHub
• [I] 请问Global Balance的bthread调度优化算法如何开启使用 (brpc) via GitHub
  • Re: [I] 请问Global Balance的bthread调度优化算法如何开启使用 (brpc) via GitHub
• Re: [I] 为什么代码方式关闭不了bvar sampling线程？ (brpc) via GitHub
• Re: [I] 添加LoongArch64架构支持 (brpc) via GitHub
• [I] Signal Trace bug has memory access problem (brpc) via GitHub
  • Re: [I] Signal Trace has memory access problem (brpc) via GitHub
  • Re: [I] Signal Trace has memory access problem (brpc) via GitHub
• [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
  • Re: [I] 在高并发场景下server直接hang死 (brpc) via GitHub
• [I] butil/base_paths.cc:5:10: fatal error: butil/base_paths.h: No such file or directory (brpc) via GitHub
  • Re: [I] butil/base_paths.cc:5:10: fatal error: butil/base_paths.h: No such file or directory (brpc) via GitHub
  • Re: [I] butil/base_paths.cc:5:10: fatal error: butil/base_paths.h: No such file or directory (brpc) via GitHub
  • Re: [I] butil/base_paths.cc:5:10: fatal error: butil/base_paths.h: No such file or directory (brpc) via GitHub
  • Re: [I] butil/base_paths.cc:5:10: fatal error: butil/base_paths.h: No such file or directory (brpc) via GitHub
• [I] fork without exec 子进程一直卡死在bthread::futex_wait_private (brpc) via GitHub
  • Re: [I] fork without exec 子进程一直卡死在bthread::futex_wait_private (brpc) via GitHub
• [I] When will couchbase 7.6 and above be supported? (brpc) via GitHub
  • Re: [I] When will couchbase 7.6 and above be supported? (brpc) via GitHub
• [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
  • Re: [I] 支持Couchbase v7.6以上版本 (brpc) via GitHub
• Re: [I] 怎么升级brpc的probuf版本 (brpc) via GitHub
• Re: [I] 启用ssl后，channel发送数据偶发core在SSL_write内部 (brpc) via GitHub
• Re: [I] thrift 协议代码错误 (brpc) via GitHub
  • Re: [I] thrift 协议代码错误 (brpc) via GitHub
• Re: [I] 发送数据出现这条日志[E1011]Connection to x.x.x.x:12345 is overcrowded，调大socket_max_unwritten_bytes依旧没有缓解 (brpc) via GitHub
  • Re: [I] 发送数据出现这条日志[E1011]Connection to x.x.x.x:12345 is overcrowded，调大socket_max_unwritten_bytes依旧没有缓解 (brpc) via GitHub
• [I] Have a question for 'Handle authentication' (brpc) via GitHub
  • Re: [I] Have a question for 'Handle authentication' (brpc) via GitHub
• [I] channel可以init两次么 (brpc) via GitHub
  • Re: [I] channel可以init两次么 (brpc) via GitHub
  • Re: [I] channel可以init两次么 (brpc) via GitHub
• [I] Channel传入CallMethod函数中done的生命周期管理问题 (brpc) via GitHub
  • Re: [I] Channel传入CallMethod函数中done的生命周期管理问题 (brpc) via GitHub
  • Re: [I] Channel传入CallMethod函数中done的生命周期管理问题 (brpc) via GitHub
• [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
  • Re: [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
  • Re: [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
  • Re: [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
  • Re: [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
  • Re: [I] task tracer 信号追踪问题讨论 (brpc) via GitHub
• [I] client 使用 snappy 压缩时，server 能正常解压，但是解压出来的数据和原始数据不一致。 (brpc) via GitHub
  • Re: [I] client 使用 snappy 压缩时，server 能正常解压，但是解压出来的数据和原始数据不一致。 (brpc) via GitHub
• Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub
  • Re: [I] RDMA failure (brpc) via GitHub

• Earlier messages