From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com [209.85.167.66]) (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 9E3BC469719 for ; Mon, 14 Sep 2020 13:18:19 +0300 (MSK) Received: by mail-lf1-f66.google.com with SMTP id y2so12783465lfy.10 for ; Mon, 14 Sep 2020 03:18:19 -0700 (PDT) Date: Mon, 14 Sep 2020 13:18:16 +0300 From: Cyrill Gorcunov Message-ID: <20200914101816.GB991329@grain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Tarantool-patches] [PATCH 2/4] xlog: introduce an error code for XlogGapError List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy Cc: tarantool-patches@dev.tarantool.org On Sat, Sep 12, 2020 at 07:25:54PM +0200, Vladislav Shpilevoy wrote: > XlogGapError object didn't have a code in ClientError code space. > Because of that it was not possible to handle the gap error > together with client errors in some switch-case statement. > > Now the gap error has a code. > > This is going to be used in applier code to handle XlogGapError > among other errors using its code instead of RTTI. > > Needed for #5287 And this one too Acked-by: Cyrill Gorcunov