From: Igor Munkin <imun@tarantool.org> To: Olga Arkhangelskaia <arkholga@tarantool.org> Cc: tarantool-patches@dev.tarantool.org, Alexander Turenko <alexander.turenko@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 1/1] box: fixed box.info:memory() Date: Thu, 16 Jul 2020 20:56:18 +0300 [thread overview] Message-ID: <20200716175618.GN5559@tarantool.org> (raw) In-Reply-To: <20200715144023.pll42732ijjw6obo@tkn_work_nb> Olya, Thanks for your updates! The patch is OK, but I still have several comments regarding it, so I pasted it below. Besides, the branch is extremely outdated and based on 2.2 (it might complicate the merge process). | box: fix box.info:memory() | | Fix the return value of box.info:memory(). It used to return the same table | as the box.info(). | | If one removes metatable of the box.info:memory(): | tarantool> setmetatable(box.info:memory(), nil) | --- | - cache: 0 | lua: 1855568 | data: 37976 | index: 1196032 | net: 589824 | tx: 0 | version: 2.5.0-158-g667145aff | package: Tarantool | | While printing the table, lbox_info_memory_call adds box.info.memory's fields to | the box.info table. To avoid this effect and return just box.info.memory we put | an empty table on the Lua stack at the beginning of the lbox_info_memory_call | function. | | Closes #4688 At first, the message still exceeds 72 symbols. Sasha has already pointed to this several times. Let's make Sasha a bit happier! Furthermore, you described why the output is the same as the one obtained via box.info, but stripped everything regarding why box.info is used here. I still guess it's worth to be mentioned, even if it is perfectly described in Lua reference manual and PIL. | diff --git a/src/box/lua/info.c b/src/box/lua/info.c | index d0e553b1d..e5b1c32f0 100644 | --- a/src/box/lua/info.c | +++ b/src/box/lua/info.c | @@ -322,6 +322,8 @@ lbox_info_memory_call(struct lua_State *L) | struct engine_memory_stat stat; | engine_memory_stat(&stat); | | + lua_newtable(L); | + I agree with Sasha, regarding <lua_createtable> usage: it can preallocate the exact required size memory area, so I see no reasons to ignore such benefit. | lua_pushstring(L, "data"); | luaL_pushuint64(L, stat.data); | lua_settable(L, -3); | diff --git a/test/box-tap/gh-4688-box-info-memory.test.lua b/test/box-tap/gh-4688-box-info-memory.test.lua | new file mode 100755 | index 000000000..8d6aa0e00 | --- /dev/null | +++ b/test/box-tap/gh-4688-box-info-memory.test.lua | @@ -0,0 +1,28 @@ | +#!/usr/bin/env tarantool | + | +-- | +-- gh-4688: box.info:memory() displayed full content of box.info | +-- | +local tap = require('tap') | + | +box.cfg() | + | +local test = tap.test('gh-4688-box.info:memory-wrong-result') | +test:plan(1) | + | +local a = box.info.memory() | +local b = box.info:memory() These variables are excess. | + | +local function get_keys(t) | + local keys = {} | + for k, v in pairs(t) do | + table.insert(keys, k) | + end | + return keys | +end | + | +local keys_1 = get_keys(box.info.memory()) | +local keys_2 = get_keys(box.info:memory()) | +test:is_deeply(keys_1, keys_2, "box.info:memory coincide with box.info.memory") | + | +os.exit(test:check() and 0 or 1) -- Best regards, IM
next prev parent reply other threads:[~2020-07-16 18:06 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20200629121118.21596-1-arkholga@tarantool.org> 2020-06-29 12:11 ` Olga Arkhangelskaia 2020-07-01 21:34 ` Igor Munkin 2020-07-02 10:01 ` Olga Arkhangelskaia 2020-07-09 1:08 ` Alexander Turenko 2020-07-09 13:57 ` Olga Arkhangelskaia 2020-07-15 14:40 ` Alexander Turenko 2020-07-16 17:56 ` Igor Munkin [this message] 2020-07-16 20:29 ` Olga Arkhangelskaia 2020-07-16 20:56 ` Alexander Turenko 2020-07-16 21:04 ` Igor Munkin 2020-07-17 6:38 ` Olga Arkhangelskaia 2020-07-01 21:34 ` [Tarantool-patches] [PATCH 0/1] fix box.info:memory() Igor Munkin 2020-07-09 1:08 ` Alexander Turenko 2020-07-09 14:02 ` Olga Arkhangelskaia 2020-07-16 18:16 ` Igor Munkin 2020-07-16 18:29 ` Alexander Turenko 2020-07-17 6:18 ` Kirill Yukhin
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=20200716175618.GN5559@tarantool.org \ --to=imun@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=arkholga@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/1] box: fixed box.info:memory()' \ /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