From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Timur Safin <tsafin@tarantool.org> Cc: alexander.turenko@tarantool.org, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 1/3] test: corrected reported error lines Date: Tue, 29 Jun 2021 19:21:05 +0300 [thread overview] Message-ID: <20210629162105.GD10212@tarantool.org> (raw) In-Reply-To: <151601d76baa$6d360c70$47a22550$@tarantool.org> Timur, On 28.06.21, Timur Safin wrote: > > : From: Igor Munkin <imun@tarantool.org> > : Subject: Re: [Tarantool-patches] [PATCH v2 1/3] test: corrected reported > : error lines > : > : Timur, > : > : Thanks for the patch! Though the change is quite trivial, the patch is > : not OK right from the top. Please adjust the commit subject according to > : our contribution guidelines[1]. > > Much thanks Sasha for his useful proposal, not thanks to Igor for useless > referring to guidelines without suggestion. Sorry, my bad. If you need a suggestion, here you are: re-read our contribution guidelines, especially the following bullet: | Use the imperative mood in the subject line. A properly formed Git | commit subject line should always be able to complete the following | sentence: "If applied, this commit will /your subject line here/". > <snipped> > : > : Minor: Strictly saying :123 part is also broken. > > O_o, why? Could you please clarify? We report it as line number in the > source file, in this case tkt-9a8b09f8e6.test.lua:123 was exactly the > caller location? Do you need the location of definition (:123) or location where the function execution is stopped at the moment (:142)? If I got your point, you prefer the latter, right? > <snipped> > : > diff --git a/src/lua/tap.lua b/src/lua/tap.lua > : > index 346724d84..77fd8d096 100644 > : > --- a/src/lua/tap.lua > : > +++ b/src/lua/tap.lua > : > @@ -23,7 +23,7 @@ local function traceback(level) > : > local frame = { > : > source = info.source; > : > src = info.short_src; > : > - line = info.linedefined or 0; > : > + line = info.currentline or info.linedefined or 0; > : > : Why did you leave such a complex code here? I believe you can use just > : info.currentline here. > > Just in case :) Nice reasoning :) > if currentline may be missing in the traceback object for any reason. It may not, considering the flags used for obtaining debug info. > If it's impossible for the set of requested flags, then I'll get rid > of linedefined here. Yes, <currentline> field is provided by 'l' flag[1]. Please, get rid of <linedefined> and the default 0 and drop a few sentences regarding this change in commit message. > > : : [1]: : > https://www.tarantool.io/en/doc/latest/dev_guide/developer_guidelines/#how- > : to-write-a-commit-message : : -- : Best regards, : IM > > Thanks, Timur > [1]: https://www.lua.org/manual/5.1/manual.html#lua_getinfo -- Best regards, IM
next prev parent reply other threads:[~2021-06-29 16:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-11 7:48 [Tarantool-patches] [PATCH v2 0/3] sql: modify explicit and implicit conversion tables Timur Safin via Tarantool-patches 2021-06-11 7:48 ` [Tarantool-patches] [PATCH v2 1/3] test: corrected reported error lines Timur Safin via Tarantool-patches 2021-06-20 18:57 ` Igor Munkin via Tarantool-patches 2021-06-23 21:01 ` Alexander Turenko via Tarantool-patches 2021-06-27 23:16 ` Timur Safin via Tarantool-patches 2021-06-29 16:21 ` Igor Munkin via Tarantool-patches [this message] 2021-06-30 6:49 ` Timur Safin via Tarantool-patches 2021-07-21 7:24 ` Igor Munkin via Tarantool-patches 2021-06-11 7:48 ` [Tarantool-patches] [PATCH v2 2/3] sql: updated explicit conversion table Timur Safin via Tarantool-patches 2021-06-20 18:52 ` Mergen Imeev via Tarantool-patches 2021-06-25 21:26 ` Timur Safin via Tarantool-patches 2021-06-25 21:26 ` [Tarantool-patches] Отзыв: " Timur Safin via Tarantool-patches 2021-06-27 23:46 ` [Tarantool-patches] " Timur Safin via Tarantool-patches 2021-06-11 7:48 ` [Tarantool-patches] [PATCH v2 3/3] sql: updated implicit " Timur Safin via Tarantool-patches 2021-06-20 18:52 ` Mergen Imeev via Tarantool-patches 2021-06-28 0:06 ` Timur Safin via Tarantool-patches 2021-06-20 18:52 ` [Tarantool-patches] [PATCH v2 0/3] sql: modify explicit and implicit conversion tables Mergen Imeev via Tarantool-patches 2021-06-27 23:29 ` Timur Safin via Tarantool-patches
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=20210629162105.GD10212@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=imun@tarantool.org \ --cc=tsafin@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 1/3] test: corrected reported error lines' \ /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