Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin <imun@tarantool.org>
To: Leonid Vasiliev <lvasiliev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 1/2] luarocks: Add a kludge for option all of luarocks search
Date: Wed, 1 Apr 2020 02:21:04 +0300	[thread overview]
Message-ID: <20200331232104.GP22874@tarantool.org> (raw)
In-Reply-To: <c5da3dc05b778a45fe7eaca5a75ba72b4ba6c203.1584358124.git.lvasiliev@tarantool.org>

Leonid,

Thanks for the patch! Please consider the comment below.

On 16.03.20, Leonid Vasiliev wrote:
> From: Leonid <lvasiliev@tarantool.org>
> 
> Fixed the tarantoolctl rocks search flag --all
> 
> Forwarding of the --all flag to tarantoolctl rocks module was added.
> (Command: tarantoolctl rocks search --all)
> 
> Fixes: #4529
> ---
>  extra/dist/tarantoolctl.in | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/extra/dist/tarantoolctl.in b/extra/dist/tarantoolctl.in
> index 6daf866ac..372838edd 100755
> --- a/extra/dist/tarantoolctl.in
> +++ b/extra/dist/tarantoolctl.in

<snipped>

> @@ -945,6 +946,10 @@ local function rocks()
>      end
>      table.insert(positional_arguments, key)
>  
> +    if positional_arguments[1] == "search" and find_arg("all") then

This is a bad check. Consider the following example:
| $ export LUA_PATH="$LUA_PATH;third_party/luarocks/src/?.lua;;"
| $ ./extra/dist/tarantoolctl rocks search --all > valid.out
| $ wc valid.out && echo "Non-empty output"
| 17835  56986 605906 valid.out
| Non-empty output
| $ ./extra/dist/tarantoolctl rocks search all --force > invalid.out
| $ diff -u valid.out invalid.out && echo "Outputs are the same"
| Outputs are the same

You need to check whether 'all' key exists in keyword_arguments, not to
search 'all' substring in arg tables values.

> +        table.insert(positional_arguments, "--all")
> +    end
> +
>      -- Tweak help messages
>      util.see_help = function(command, program)
>          -- TODO: print extended help message here

<snipped>

> -- 
> 2.17.1
> 

-- 
Best regards,
IM

  parent reply	other threads:[~2020-03-31 23:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 11:50 [Tarantool-patches] [PATCH v2 0/2] Fix some options of rocks module Leonid Vasiliev
2020-03-16 11:50 ` [Tarantool-patches] [PATCH v2 1/2] luarocks: Add a kludge for option all of luarocks search Leonid Vasiliev
2020-03-16 12:01   ` Leonid Vasiliev
2020-03-31 23:21   ` Igor Munkin [this message]
2020-04-01 10:00     ` lvasiliev
2020-04-02 15:50       ` lvasiliev
2020-03-16 11:50 ` [Tarantool-patches] [PATCH v2 2/2] luarocks: Add a kludge for option force of luarocks remove Leonid Vasiliev
2020-03-31 23:21   ` Igor Munkin
2020-04-01 10:02     ` lvasiliev
2020-04-02 15:52       ` lvasiliev
2020-03-18 22:34 ` [Tarantool-patches] [PATCH v2 0/2] Fix some options of rocks module Vladislav Shpilevoy
2020-03-19 19:19   ` Igor Munkin
2020-04-01 11:33 ` Igor Munkin
2020-04-02  7:35   ` lvasiliev
2020-04-02 15:34 ` Kirill Yukhin
2020-04-09  1:00   ` Alexander Turenko
2020-04-04 18:40 ` Vladislav Shpilevoy

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=20200331232104.GP22874@tarantool.org \
    --to=imun@tarantool.org \
    --cc=lvasiliev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2 1/2] luarocks: Add a kludge for option all of luarocks search' \
    /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