From: Nikita Pettik <korablev@tarantool.org> To: Maria <maria.khaydich@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH] box.execute should be immutable function Date: Thu, 14 Nov 2019 19:51:30 +0300 [thread overview] Message-ID: <20191114165130.GB37401@tarantool.org> (raw) In-Reply-To: <20191114115020.21091-1-maria.khaydich@tarantool.org> On 14 Nov 14:50, Maria wrote: > Using box.execute method before explicitly > configuring box automatically invoked box.cfg > nonetheless. Any further calls to the latter > caused its reconfiguration which could lead > to an error when trying to use the method. Hello. I'm not going to comment patch iteself, just want to leave a couple of general nits. They are just recommendations. Feel free to use up to 72 characters while making up commit's body. I'd fix commit subject: box.execute should be immutable -> box: make box.execute() immutable despite box.cfg{} (or sort of). > Closes #4231 > Issue: > https://github.com/tarantool/tarantool/issues/4231 > Branch: > https://github.com/tarantool/tarantool/compare/eljashm/gh-4231-box.execute-immutable-function Please, put links under --- delimiter so that it will be ignored by git am. > --- > src/box/lua/load_cfg.lua | 4 +++- > test/box-tap/execute.test.lua | 17 +++++++++++++++++ > 2 files changed, 20 insertions(+), 1 deletion(-) > create mode 100755 test/box-tap/execute.test.lua > > diff --git a/src/box/lua/load_cfg.lua b/src/box/lua/load_cfg.lua > index e7f62cf4e..042edf913 100644 > --- a/src/box/lua/load_cfg.lua > +++ b/src/box/lua/load_cfg.lua > @@ -528,7 +528,9 @@ box.cfg = locked(load_cfg) > -- metatable. > -- > function box.execute(...) > - load_cfg() > + if not box.cfg then > + load_cfg() > + end > return box.execute(...) > end > > diff --git a/test/box-tap/execute.test.lua b/test/box-tap/execute.test.lua > new file mode 100755 > index 000000000..301cf4a1c > --- /dev/null > +++ b/test/box-tap/execute.test.lua I'd better name this test ..box-tap/gh-4231-immutable-execute-func.test.lua It is generally accepted naming way. > @@ -0,0 +1,17 @@ > +#!/usr/bin/env tarantool > + > +local tap = require('tap') > +local test = tap.test('execute') > +test:plan(1) Please, leave comment explaining what exactly is tested here. For instance: -- Make sure that box.execute() method does not change after -- the very first box.cfg{} invokation. -- > + > +local box_execute = box.execute > +box.cfg{} > + > +local status, err = pcall( > + function() > + box_execute("CREATE TABLE t1 (s1 INTEGER, PRIMARY KEY (s1));") > + end) > + > +test:ok(status and err == nil, "box.execute after box.cfg") I guess this should be error message which is displayed in case test fails. If so, I'd rather use message like: "box.execute() is changed after box.cfg{} invokation"
next prev parent reply other threads:[~2019-11-14 16:51 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-14 11:50 Maria 2019-11-14 16:51 ` Nikita Pettik [this message] 2019-12-17 14:39 ` Igor Munkin 2019-12-24 15:32 ` [Tarantool-patches] [PATCH] box: make box.execute() immutable Maria Khaydich 2019-12-25 1:30 ` Igor Munkin 2019-12-26 14:08 ` Alexander Turenko 2020-01-13 12:13 ` Maria Khaydich 2020-01-13 15:48 ` Igor Munkin 2020-01-18 10:56 ` Maria Khaydich 2020-02-20 17:51 ` Alexander Turenko 2020-02-20 21:15 ` Igor Munkin 2020-03-11 15:56 ` Maria Khaydich 2020-03-18 22:25 ` Igor Munkin 2020-05-02 14:52 ` Alexander Turenko 2020-05-12 16:16 ` Alexander Turenko 2020-03-11 15:57 ` [Tarantool-patches] [PATCH 1/2] box: make box.cfg idempotent function Maria Khaydich 2020-03-12 13:29 ` Konstantin Osipov 2020-03-12 19:25 ` Maria Khaydich 2020-03-12 20:00 ` Konstantin Osipov 2020-03-18 22:26 ` Igor Munkin 2020-03-19 7:19 ` Konstantin Osipov 2020-03-19 9:08 ` Igor Munkin 2020-03-19 10:06 ` Konstantin Osipov 2020-03-19 10:26 ` Igor Munkin 2020-05-06 11:17 ` Alexander Turenko 2020-05-06 11:49 ` Konstantin Osipov 2020-05-06 12:53 ` Alexander Turenko 2020-05-06 13:02 ` Konstantin Osipov 2020-05-06 13:13 ` Alexander Turenko 2020-03-18 22:26 ` Igor Munkin 2020-05-12 16:17 ` Alexander Turenko
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=20191114165130.GB37401@tarantool.org \ --to=korablev@tarantool.org \ --cc=maria.khaydich@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH] box.execute should be immutable function' \ /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