gooddbird / tinyrpc Goto Github PK

这两个文件是否需要更新一下与quick_rpc_test.md保持一致😀
在test_rpc_server1.cc文件中会休眠6s

DebugLog << "this is query_name func";
DebugLog << "first begin to sleep 6s";
sleep_hook(6);
DebugLog << "sleep 6s end";

而在test_rpc_server2.cc中tcp_connection的超时时间为1s。

rpc_controller.SetTimeout(1000);

导致在使用测试用例时，会出现包发出去还没收到，此时就超时了，导致无法看到返回结果，会让人感到疑惑
[2022-05-18 12:19:25.94814] [INFO] [53269] [53269] [1] [tinyrpc/net/tcp/tcp_connection.cc:214] send[79] bytes data to [127.0.0.1:39999], fd [13]
[2022-05-18 12:19:25.94839] [INFO] [53269] [53269] [1] [tinyrpc/net/tcp/tcp_connection.cc:217] send all data, now unregister write event and break
[2022-05-18 12:19:25.94865] [DEBUG] [53269] [53269] [1] [tinyrpc/net/tcp/tcp_connection.cc:279] 82061641944973154118|reply data not exist
[2022-05-18 12:19:25.94889] [DEBUG] [53269] [53269] [1] [tinyrpc/net/tcp/tcp_connection.cc:114] m_read_buffer size=128rd=0wd=0
[2022-05-18 12:19:25.94914] [DEBUG] [53269] [53269] [1] [tinyrpc/coroutine/coroutine_hook.cc:55] this is hook read
[2022-05-18 12:19:25.94956] [DEBUG] [53269] [53269] [1] [tinyrpc/net/fd_event.cc:120] fd already set o_nonblock
[2022-05-18 12:19:25.94984] [DEBUG] [53269] [53269] [1] [tinyrpc/coroutine/coroutine_hook.cc:34] fd:[13], register read event to epoll
[2022-05-18 12:19:25.95009] [DEBUG] [53269] [53269] [1] [tinyrpc/net/reactor.cc:179] epoll_ctl add succ, fd[13]
[2022-05-18 12:19:25.95031] [DEBUG] [53269] [53269] [1] [tinyrpc/coroutine/coroutine_hook.cc:87] read func to yield
[2022-05-18 12:19:26.55967] [INFO] [53269] [53269] [0] [tinyrpc/net/tcp/tcp_client.cc:49] TcpClient timer out event occur

问个无关问题，协议可以用json吗

google/protobuf是多少版本？只能是3.0.19吗

大佬请问一下，是否对libmysqlclient.a版本有具体要求？我装的是mysql版本是5.7.33

文中的版本是2，但代码好像没有指定，然后找不到文件编译失败？

1. 是否支持多线程? sylar是一个假的"多线程" 是否支持协程线程绑定?
2. hook里函数不建议与libc同名 sylar-yin/sylar#15

”注意将头文件和库文件 copy 到对应的系统路径下。“
这是指的把哪些文件放在哪里啊？

void TcpBuffer::recycleWrite(int index) {
  int j = m_write_index + index;
  //TODO: here get a bug
  if (j >= (int)m_buffer.size()) {
    ErrorLog << "recycleWrite error";
    return;
  }
  m_write_index = j;
  adjustBuffer();
}

此处是否有bug，当buffer被填满时，例如
[2022-05-18 03:04:04.214972] [DEBUG] [29062] [29064] [1] [tinyrpc/net/tcp/tcp_connection.cc:114] m_read_buffer size=128rd=0wd=0
[2022-05-18 03:04:04.214988] [DEBUG] [29062] [29064] [1] [tinyrpc/coroutine/coroutine_hook.cc:55] this is hook read
[2022-05-18 03:04:04.214998] [DEBUG] [29062] [29064] [1] [tinyrpc/net/fd_event.cc:121] fd already set o_nonblock
[2022-05-18 03:04:04.215017] [DEBUG] [29062] [29064] [1] [tinyrpc/net/tcp/tcp_connection.cc:116] read_hook func get size: 128
此时读到了128个byte，但是在调用recycleWrite时，由于0+128 >= 128而导致返回，引发后续错误

(gdb) bt
#0 0x000055ef99818064 in tinyrpc::Coroutine::Coroutine (this=0x55ef9b3c1b80) at /usr/include/c++/9/bits/shared_ptr_base.h:1020
#1 0x000055ef99818bfd in tinyrpc::Coroutine::Coroutine(int, char*, std::function<void ()>) (this=0x55ef9b3c2180, size=, stack_ptr=, cb=...)
at tinyrpc/coroutine/coroutine.cc:87
#2 0x000055ef99816c05 in __gnu_cxx::new_allocatortinyrpc::Coroutine::construct<tinyrpc::Coroutine, int&, char*&, void (&)()> (__p=0x55ef9b3c2180, this=)
at /usr/include/c++/9/new:174
#3 std::allocator_traits<std::allocatortinyrpc::Coroutine >::construct<tinyrpc::Coroutine, int&, char*&, void (&)()> (__p=0x55ef9b3c2180, __a=...) at /usr/include/c++/9/bits/alloc_traits.h:483
#4 std::_Sp_counted_ptr_inplace<tinyrpc::Coroutine, std::allocatortinyrpc::Coroutine, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<int&, char*&, void (&)()> (__a=..., this=0x55ef9b3c2170)
at /usr/include/c++/9/bits/shared_ptr_base.h:548
#5 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<tinyrpc::Coroutine, std::allocatortinyrpc::Coroutine, int&, char*&, void (&)()> (__a=..., __p=,
this=) at /usr/include/c++/9/bits/shared_ptr_base.h:679
#6 std::__shared_ptr<tinyrpc::Coroutine, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocatortinyrpc::Coroutine, int&, char*&, void (&)()> (__tag=..., this=)
at /usr/include/c++/9/bits/shared_ptr_base.h:1344
#7 std::shared_ptrtinyrpc::Coroutine::shared_ptr<std::allocatortinyrpc::Coroutine, int&, char*&, void (&)()> (__tag=..., this=) at /usr/include/c++/9/bits/shared_ptr.h:359
#8 std::allocate_shared<tinyrpc::Coroutine, std::allocatortinyrpc::Coroutine, int&, char*&, void (&)()> (__a=...) at /usr/include/c++/9/bits/shared_ptr.h:702
#9 std::make_shared<tinyrpc::Coroutine, int&, char*&, void (&)()> () at /usr/include/c++/9/bits/shared_ptr.h:718
#10 main (argc=, argv=) at testcases/test_coroutine.cc:44

排查后原因在于 coctx_swap.S 似乎只支持了x86架构，支持arm64的代码可以从这里copy ：https://github.com/Ananfa/libcorpc/blob/master/co/src/coctx_swap.S。本人新手，希望作者可以帮忙一起看看

测试代码中没有找到继承并实现query_service_stub

/usr/local/include/absl/base/policy_checks.h:79:2: error: #error "C++ versions less than C++14 are not supported."
这个问题是因为什么呢？怎么解决呢？

第一次make时protobuf显式至少C++版本至少是C++14, 手动修改makefile的编译选项为-std=c++14之后有如下链接问题

/usr/bin/ld: extension_set.cc:(.text+0x906e): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::~LogMessageFatal()'
/usr/bin/ld: /usr/local/lib/libprotobuf.a(extension_set.cc.o): in function `google::protobuf::internal::ExtensionSet::SetRepeatedEnum(int, int, int)':
extension_set.cc:(.text+0x910e): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::LogMessageFatal(char const*, int, std::basic_string_view<char, std::char_traits<char> >)'
/usr/bin/ld: extension_set.cc:(.text+0x9150): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::~LogMessageFatal()'
/usr/bin/ld: extension_set.cc:(.text+0x91d7): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::LogMessageFatal(char const*, int, std::basic_string_view<char, std::char_traits<char> >)'
/usr/bin/ld: extension_set.cc:(.text+0x91ef): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::~LogMessageFatal()'
/usr/bin/ld: extension_set.cc:(.text+0x9270): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::LogMessageFatal(char const*, int, std::basic_string_view<char, std::char_traits<char> >)'
/usr/bin/ld: extension_set.cc:(.text+0x9288): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::~LogMessageFatal()'
/usr/bin/ld: extension_set.cc:(.text+0x92c6): undefined reference to `absl::lts_20230125::log_internal::LogMessageFatal::~LogMessageFatal()

protobuf版本

CMake Error at /usr/local/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find Protobuf (missing: Protobuf_LIBRARIES Protobuf_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/local/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
/usr/local/share/cmake-3.27/Modules/FindProtobuf.cmake:652 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:28 (find_package)
用cmake方式编译时出错，这是为什么

When I compile the project, the error message is
In file included from tinyrpc/comm/log.cc:16: tinyrpc/comm/config.h:4:10: fatal error: tinyxml/tinyxml.h: No such file or directory
How should I solve it?

您好，我看到业务接口是通过.proto文件定义的，我的理解是protobuf根据这个文件来做序列化反序列化。但是tinypb实际上也自己规定了一些字段，其中就包含了.proto消息序列化后的字符串，而tinypb在代码里是手动序列化反序列化的。我的问题是，为什么不直接全部用protobuf来处理rpc通信的消息，而要在外层封装一层tinypb还要手动序列化呢？

（刚接触rpc，之前没有实际业务经验，目前正在通过您的项目学习这一块的内容。）

想问下作者，在调用QueryServiceImpl::query_name这个服务的时候，当执行到instase初始化那一行代码的时候服务器就崩溃了。我本地自己起了一个mysql数据库，然后配置文件中的mysql相应配置部分内容也改了，并且我自己写了一个小demo来测试mysql的连接状况，也没出什么问题。所以想问问作者，这可能是什么原因导致的呢，疑惑好几天了....

安装完成后想运行一下testcast的例子，运行失败了。运行的命令如下

g++ test_tinypb_server.cc ../lib/libtinyrpc.a -o test_tinypb_server 

报的错误是找不相关引用，比如：

/usr/bin/ld: /tmp/ccBramt5.o:(.data.rel.ro._ZTV16QueryServiceImpl[_ZTV16QueryServiceImpl]+0x30): undefined reference to `QueryService::GetRequestPrototype(google::protobuf::MethodDescriptor const*) const'

和

/root/tinyrpc-main/tinyrpc/comm/config.cc:31: undefined reference to `TiXmlElement::GetText() const'
/usr/bin/ld: /root/tinyrpc-main/tinyrpc/comm/config.cc:35: undefined reference to `TiXmlElement::GetText() const'