From: Oleg Babin <olegrok@tarantool.org> To: Cyrill Gorcunov <gorcunov@gmail.com>, tml <tarantool-patches@dev.tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v8 10/12] log/lua: allow to specify logging level as a string Date: Wed, 3 Jun 2020 10:03:24 +0300 [thread overview] Message-ID: <2ce5c32b-f0fc-3593-7617-de1b0de8f5e8@tarantool.org> (raw) In-Reply-To: <20200602221817.645015-11-gorcunov@gmail.com> Hi! Thanks for changes, see one comment below. On 03/06/2020 01:18, Cyrill Gorcunov wrote: > Allow to specify logging level as a string in log.cfg() call. > > @TarantoolBot document > Title: Module log > > The `log.cfg({level='string'})` accepts not only number but > symbolic representation of loglevels such as: `fatal`, `syserror`, > `error`, `crit`, `warn`, `info`, `verbose` and `debug`. > > Part-of #689 > > Suggested-by: Oleg Babin <olegrok@tarantool.org> > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> > --- > src/lua/log.lua | 36 ++++++++++++++++++++++++++++++++++-- > test/app-tap/logger.test.lua | 29 ++++++++++++++++++++++++++++- > 2 files changed, 62 insertions(+), 3 deletions(-) > > diff --git a/src/lua/log.lua b/src/lua/log.lua > index 33f7a5892..50c96a8d2 100644 > --- a/src/lua/log.lua > +++ b/src/lua/log.lua > @@ -140,6 +140,26 @@ local function update_box_cfg(k) > end > end > > +-- Logging levels symbolic representation. > +local log_level_keys = { > + ['fatal'] = ffi.C.S_FATAL, > + ['syserror'] = ffi.C.S_SYSERROR, > + ['error'] = ffi.C.S_ERROR, > + ['crit'] = ffi.C.S_CRIT, > + ['warn'] = ffi.C.S_WARN, > + ['info'] = ffi.C.S_INFO, > + ['verbose'] = ffi.C.S_VERBOSE, > + ['debug'] = ffi.C.S_DEBUG, > +} > + > +local function log_level_list() > + local keyset = {} > + for k in pairs(log_level_keys) do > + keyset[#keyset + 1] = k > + end > + return table.concat(keyset, ',') > +end > + > local function say(level, fmt, ...) > if ffi.C.log_level < level then > -- don't waste cycles on debug.getinfo() > @@ -303,8 +323,20 @@ local function load_cfg(oldcfg, cfg) > end > > if cfg.level ~= nil then > - if type(cfg.level) ~= 'number' then > - error("log: 'level' option must be a number") > + if type(cfg.level) == 'number' then > + if cfg.level < ffi.C.S_FATAL or > + cfg.level > ffi.C.S_DEBUG then > + local m = "log: 'level' must be in range [%d;%d]" > + error(m:format(ffi.C.S_FATAL, ffi.C.S_DEBUG)) > + end > + elseif type(cfg.level) == 'string' then > + if log_level_keys[cfg.level] == nil then > + local m = "log: 'level' must be one of [%s]" > + error(m:format(log_level_list())) > + end > + cfg.level = log_level_keys[cfg.level] > + else > + error("log: 'level' must be a number or string") > end > end > > diff --git a/test/app-tap/logger.test.lua b/test/app-tap/logger.test.lua > index bc301d720..48dc8af3e 100755 > --- a/test/app-tap/logger.test.lua > +++ b/test/app-tap/logger.test.lua > @@ -1,7 +1,7 @@ > #!/usr/bin/env tarantool > > local test = require('tap').test('log') > -test:plan(34) > +test:plan(44) > > -- gh-3946: Assertion failure when using log_format() before box.cfg() > local log = require('log') > @@ -60,6 +60,33 @@ log.cfg({format='plain', level=5}) > test:is(box.cfg.log_format, 'plain', 'box sees plain format') > test:is(box.cfg.log_level, 5, 'box sees level change') > > +-- Test symbolic names for loglevels > +log.cfg({level='fatal'}) > +test:ok(log.cfg.level == 0 and box.cfg.log_level == 0, 'both got fatal') > +log.cfg({level='syserror'}) > +test:ok(log.cfg.level == 1 and box.cfg.log_level == 1, 'both got syserror') > +log.cfg({level='error'}) > +test:ok(log.cfg.level == 2 and box.cfg.log_level == 2, 'both got error') > +log.cfg({level='crit'}) > +test:ok(log.cfg.level == 3 and box.cfg.log_level == 3, 'both got crit') > +log.cfg({level='warn'}) > +test:ok(log.cfg.level == 4 and box.cfg.log_level == 4, 'both got warn') > +log.cfg({level='info'}) > +test:ok(log.cfg.level == 5 and box.cfg.log_level == 5, 'both got info') > +log.cfg({level='verbose'}) > +test:ok(log.cfg.level == 6 and box.cfg.log_level == 6, 'both got verbose') > +log.cfg({level='debug'}) > +test:ok(log.cfg.level == 7 and box.cfg.log_level == 7, 'both got debug') > + > +_,err = pcall(log, {level = -1}) > +test:ok(err ~= nil, 'level = -1 error') > + > +_,err = pcall(log, {level = 'unknown'}) > +test:ok(err ~= nil, "level = 'unknown' error") > + ``` tarantool> pcall(log, {level = -1}) --- - false - attempt to call a table value ... tarantool> pcall(log, {level = 'unknown'}) --- - false - attempt to call a table value ... ``` It should be pcall(log.cfg, ...). Also it would be nice to check that error message is "log: 'level' must be one of...". > +-- restore to info for next tests > +log.cfg({level='info'}) > + > -- > -- Check that Tarantool creates ADMIN session for #! script > -- >
next prev parent reply other threads:[~2020-06-03 7:03 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-02 22:18 [Tarantool-patches] [PATCH v8 00/12] lua/log: add an ability to setup logger without box.cfg{} Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 01/12] core/say: do not reconfig early set up logger Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 02/12] core/say: use say_logger_initialized in say_logger_free Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 03/12] lua/log: declare say_logger_init and say_logger_initialized Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 04/12] lua/log: put string constants to map Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 05/12] lua/log: do not allow to set json for boot logger Cyrill Gorcunov 2020-06-03 6:59 ` Oleg Babin 2020-06-03 7:34 ` Cyrill Gorcunov 2020-06-03 9:44 ` Kirill Yukhin 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 06/12] lua/log: declare log as separate variable Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 07/12] lua/log: use log module settings inside box.cfg Cyrill Gorcunov 2020-06-03 7:00 ` Oleg Babin 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 08/12] lua/log: allow to configure logging without a box Cyrill Gorcunov 2020-06-03 7:01 ` Oleg Babin 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 09/12] test: logger -- use log module directly Cyrill Gorcunov 2020-06-03 7:02 ` Oleg Babin 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 10/12] log/lua: allow to specify logging level as a string Cyrill Gorcunov 2020-06-03 7:03 ` Oleg Babin [this message] 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 11/12] lua/log: use log_cfg instead of ffi's instances Cyrill Gorcunov 2020-06-02 22:18 ` [Tarantool-patches] [PATCH v8 12/12] test: logger -- consider more cases Cyrill Gorcunov 2020-06-03 7:03 ` Oleg Babin 2020-06-03 6:59 ` [Tarantool-patches] [PATCH v8 00/12] lua/log: add an ability to setup logger without box.cfg{} Oleg Babin 2020-06-03 7:09 ` Oleg Babin
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=2ce5c32b-f0fc-3593-7617-de1b0de8f5e8@tarantool.org \ --to=olegrok@tarantool.org \ --cc=gorcunov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v8 10/12] log/lua: allow to specify logging level as a string' \ /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