From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, Kirill Shcherbatov <kshcherbatov@tarantool.org> Cc: alexander.turenko@tarantool.org, kostja@tarantool.org Subject: [tarantool-patches] Re: [PATCH v1 2/3] box: stacked diagnostics area in fiber Date: Mon, 5 Aug 2019 23:16:06 +0200 [thread overview] Message-ID: <ef1f672c-b80c-1e1b-86c4-5a96143cc826@tarantool.org> (raw) In-Reply-To: <0788e7745432f2ff59be4578db0daf0c632900ed.1564657285.git.kshcherbatov@tarantool.org> Thanks for the patch! See 2 comments below. On 01/08/2019 13:13, Kirill Shcherbatov wrote: > This patch introduces stacked errors. A new API diag_add allows > to extend an existent error information with a new one error. 1. 'a' assumes singular. You can and usually should omit 'one'. > The previous state becomes a "reason" of the last-set error. > Each error object takes a reference to it's reason error object. > > The :unpack() method patched correspondingly to display the whole > errors trace. > > Part of #1148 > --- > diff --git a/test/engine/func_index.result b/test/engine/func_index.result > index 877b76d5e..ae8873c9b 100644 > --- a/test/engine/func_index.result > +++ b/test/engine/func_index.result > @@ -189,6 +188,16 @@ s:insert({1}) > | - error: 'Key format doesn''t match one defined in functional index ''idx'' of space > | ''withdata'': to many values were returned' > | ... > +box.error.last():unpack() > + | --- > + | - - type: ClientError > + | code: 199 > + | message: 'Key format doesn''t match one defined in functional index ''idx'' of > + | space ''withdata'': to many values were returned' > + | trace: > + | - file: /home/kir/WORK/tarantool/src/box/key_list.c > + | line: 95 2. Firstly, if you change something on the branch, then please, write about in an email. On the branch I see that you added filters. Lets filter out the line as well. Otherwise that test will fail each time we add or delete any of first 95 lines of key_list.c. > + | ... > idx:drop() > | --- > | ...
next prev parent reply other threads:[~2019-08-05 21:13 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-01 11:13 [tarantool-patches] [PATCH v1 0/3] " Kirill Shcherbatov 2019-08-01 11:13 ` [tarantool-patches] [PATCH v1 1/3] box: rfc for stacked diagnostic area in Tarantool Kirill Shcherbatov 2019-08-05 21:16 ` [tarantool-patches] " Vladislav Shpilevoy [not found] ` <06bd2140-3d2b-4bc3-7bc4-5f3d293bf891@tarantool.org> 2019-08-06 20:50 ` Vladislav Shpilevoy 2019-08-07 23:27 ` Alexander Turenko 2019-08-08 20:46 ` Vladislav Shpilevoy 2019-08-08 23:29 ` Alexander Turenko 2019-08-09 19:25 ` Vladislav Shpilevoy 2019-08-12 20:35 ` Konstantin Osipov 2019-08-01 11:13 ` [tarantool-patches] [PATCH v1 2/3] box: stacked diagnostics area in fiber Kirill Shcherbatov 2019-08-05 21:16 ` Vladislav Shpilevoy [this message] 2019-08-01 11:13 ` [tarantool-patches] [PATCH v1 3/3] box: extend ffi error object API Kirill Shcherbatov 2019-08-05 21:18 ` [tarantool-patches] " Vladislav Shpilevoy 2019-08-06 7:56 ` Kirill Shcherbatov 2019-08-06 20:50 ` Vladislav Shpilevoy 2019-08-08 23:33 ` Alexander Turenko 2019-08-09 19:27 ` Vladislav Shpilevoy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ef1f672c-b80c-1e1b-86c4-5a96143cc826@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=kostja@tarantool.org \ --cc=kshcherbatov@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v1 2/3] box: stacked diagnostics area in fiber' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox