From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f67.google.com (mail-lf1-f67.google.com [209.85.167.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id BB11A45C316 for ; Tue, 14 Apr 2020 15:32:36 +0300 (MSK) Received: by mail-lf1-f67.google.com with SMTP id m19so9183161lfq.13 for ; Tue, 14 Apr 2020 05:32:36 -0700 (PDT) Date: Tue, 14 Apr 2020 15:32:34 +0300 From: Cyrill Gorcunov Message-ID: <20200414123234.GG3072@uranus> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 11/12] popen: clarify popen_read_timeout error message List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Turenko Cc: tarantool-patches@dev.tarantool.org On Tue, Apr 14, 2020 at 02:38:20PM +0300, Alexander Turenko wrote: > Popen backend errors should be meaningful for a user of the popen Lua > API, because otherwise we'll need to map backend errors into Lua API > errors. This particular failure can't appear when the function is called > from the Lua API, but it is good to keep all error messages in one > style. > > Part of #4031 Acked-by: Cyrill Gorcunov