Glauber Costa 28f315fad4 system_keyspace: keep msg alive when needed
Fixes #266

Some callsites are fine: if we just get the message and process it, as is the
case with check_health for instance, msg will be alive and all is good. But if
we return a future inside the processing, msg must be kept alive. Classic bug,
appearing again.

Pekka saw this in practice in another bug. We haven't seen anything that is
related to this, but it is certainly wrong.

Signed-off-by: Glauber Costa <glommer@cloudius-systems.com>
2015-09-03 09:11:07 +03:00
2015-08-27 11:01:08 +03:00
2015-01-05 14:13:31 +08:00
2015-09-02 17:31:15 +03:00
2015-08-18 15:48:36 +03:00
2014-10-23 10:46:55 +03:00
2015-07-27 10:14:02 +03:00
2015-08-07 09:30:53 -05:00
2015-03-05 18:11:37 +02:00
2015-09-02 06:01:38 +03:00
2015-05-21 15:17:34 +03:00
2015-06-24 13:09:51 +03:00
2015-07-31 16:27:55 +08:00
2015-08-02 16:07:42 +03:00
2015-08-31 13:35:26 +03:00
2015-08-31 13:35:26 +03:00
2015-08-28 14:39:46 +03:00
2015-04-24 18:01:01 +02:00

#Urchin

##Building Urchin

In addition to required packages by Seastar, the following packages are required by Urchin.

Submodules

Urchin uses submodules, so make sure you pull the submodules first by doing:

git submodule init
git submodule update --recursive

Building urchin on Fedora

Installing required packages:

sudo yum install yaml-cpp-devel lz4-devel zlib-devel snappy-devel jsoncpp-devel thrift-devel antlr3-tool antlr3-C++-devel libasan libubsan

Building urchin on Ubuntu 14.04

Installing required packages:

sudo apt-get install libyaml-cpp-dev liblz4-dev zlib1g-dev libsnappy-dev libjsoncpp-dev
Description
No description provided
Readme 523 MiB
Languages
C++ 72.1%
Python 26.7%
CMake 0.3%
GAP 0.3%
Shell 0.3%