Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Nikita Pettik <korablev@tarantool.org>
Cc: v.shpilevoy@tarantool.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2] iproto: add an empty body to the unprepare response
Date: Fri, 6 Mar 2020 20:27:01 +0300	[thread overview]
Message-ID: <20200306172701.sziodfignjz2ix6a@tkn_work_nb> (raw)
In-Reply-To: <20200305084135.GC9655@tarantool.org>

On Thu, Mar 05, 2020 at 08:41:35AM +0000, Nikita Pettik wrote:
> On 05 Mar 08:41, Kirill Yukhin wrote:
> > Hello,
> > 
> > On 03 мар 19:16, Chris Sosnin wrote:
> > > Absence of the body in the unprepare response forces users to perform
> > > additional checks to avoid errors. Adding an empty body fixes this problem.
> > > 
> > > Closes #4769
> > > ---
> > > branch: https://github.com/tarantool/tarantool/tree/ksosnin/gh-4769-unprepare-response-body
> > > issue: https://github.com/tarantool/tarantool/issues/4769
> > > 
> > > As Nikita suggested, I created box/iproto.test.lua, and basically
> > > inserted wrappers for requests testing from box-py for future usage.
> > 
> > Could you please rename the test to be not so generic?
> > Like box/gh-4769-iproto-unprep-body or whatever.
> 
> Kirill, this test is going to assemble all iproto-related tests
> which don't rely on net.box module. Setting up all preparations
> required for raw iproto communication results in duplicating ~30-40
> lines of code in each test file.

Technically there are two ways to extract helpers from a 'core =
tarantool' test:

* Add it to, say, test/box/box.lua and to _G.protected_globals.
* Add it to a separate Lua file in test/box/lua and to 'lua_libs' field
  in test/box/suite.ini. After this you can use `require` for this
  module in a test.

So technically you're not blocked here. Both ways are available and
don't lead to much code duplication, but the process (SOP) requires to
add a test for a bug to a separate file. (Personally I still don't sure
it is good, but anyway.)

NB: 'receive', not 'recieve'. Very often typo.

WBR, Alexander Turenko.

  reply	other threads:[~2020-03-06 17:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 16:16 Chris Sosnin
2020-03-03 22:33 ` Vladislav Shpilevoy
2020-03-04  8:14   ` Chris Sosnin
2020-03-04 22:39     ` Vladislav Shpilevoy
2020-03-05  5:41 ` Kirill Yukhin
2020-03-05  8:41   ` Nikita Pettik
2020-03-06 17:27     ` Alexander Turenko [this message]
2020-03-06 19:58       ` Chris Sosnin
2020-03-06 20:39         ` Alexander Turenko
2020-03-07 22:02         ` Nikita Pettik
2020-03-08 17:13           ` Alexander Turenko
2020-03-15 15:34       ` Vladislav Shpilevoy
2020-03-17  8:04         ` Kirill Yukhin
2020-03-16 20:33 ` Konstantin Osipov

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=20200306172701.sziodfignjz2ix6a@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2] iproto: add an empty body to the unprepare response' \
    /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