兰州小红鸡
兰州小红鸡
The reason for this problem is that the `apache::thrift::HeaderServerChannel::HeaderRequest::isOneway()` function in the thrift library does not do null pointer verification - thrift\lib\cpp2\async\HeaderServerChannel.h ``` class HeaderRequest final : public ResponseChannelRequest {...
this is my patch ``` diff -ur a/thrift/lib/cpp2/async/HeaderServerChannel.h b/thrift/lib/cpp2/async/HeaderServerChannel.h --- a/thrift/lib/cpp2/async/HeaderServerChannel.h 2022-08-18 16:27:45.353299307 +0800 +++ b/thrift/lib/cpp2/async/HeaderServerChannel.h 2022-08-18 16:27:28.453299912 +0800 @@ -108,6 +108,10 @@ } bool isOneway() const override { +...
> Seems already addressed by https://github.com/vesoft-inc/nebula-third-party/blob/release-3.3/project/patches/fbthrift-2021-11-29.patch ? Oh, that's great. Since I'm still using the v3.0 version, I didn't find it fixed.
> what's your nebulagraph core version? v3.2.1
> This is triggered when the storage is started. It seems that an infinite loop occurs because the same commitLogId is submitted each time.
没推广哈，做着玩的
那是旧版本的，新版关了