On 04/21/2017 12:18 PM, Peter Lieven wrote:
Am 18.04.2017 um 12:27 schrieb Denis V. Lunev:
From: Anton Nefedov
We should wait for other coroutines on error path, i.e. one of coroutines
terminates with i/o error, before cleaning the common structures. In the
other case we would crash in a lot o
Am 18.04.2017 um 12:27 schrieb Denis V. Lunev:
> From: Anton Nefedov
>
> We should wait for other coroutines on error path, i.e. one of coroutines
> terminates with i/o error, before cleaning the common structures. In the
> other case we would crash in a lot of different places. This behaviour
> w
Am 18.04.2017 um 12:27 schrieb Denis V. Lunev:
From: Anton Nefedov
We should wait for other coroutines on error path, i.e. one of coroutines
terminates with i/o error, before cleaning the common structures. In the
other case we would crash in a lot of different places. This behaviour
was introd
From: Anton Nefedov
We should wait for other coroutines on error path, i.e. one of coroutines
terminates with i/o error, before cleaning the common structures. In the
other case we would crash in a lot of different places. This behaviour
was introduced by commit 2d9187bc65.
Signed-off-by: Anton
