From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@freelists.org, Alexander Turenko <alexander.turenko@tarantool.org> Subject: [tarantool-patches] Re: [PATCH v2 3/3] lua-yaml: treat an empty document/value as null Date: Fri, 25 Jan 2019 00:26:49 +0300 [thread overview] Message-ID: <0a841ae0-f03f-5406-5a2e-d3fc81843784@tarantool.org> (raw) In-Reply-To: <be09222062ccbd971fa3b39b760b43735d5ba334.1548123025.git.alexander.turenko@tarantool.org> Thanks for the patch! On 22/01/2019 05:12, Alexander Turenko wrote: > It improves our compatibility with the YAML standard. > > yaml.encode('') result changed from > > --- > ... > > to > > --- '' > ... > > yaml.decode('') returns zero values count before, now it returns > box.NULL. yaml.decode('- ') returns {''} before, now {box.NULL}. > > This commit touches many tests and test result files, which use console, > without behaviour changes. It also adds two test cases to > app-tap/console.test.lua. Not sure if it makes sense listing factual changes here, because literally the same I see below and in "git diff --stat". > --- > test/app-tap/console.test.lua | 16 +- > test/app/fio.result | 2 +- > test/app/socket.result | 26 +- > test/box/access.result | 8 +- > test/box/role.result | 8 +- > test/box/sequence.result | 2 +- > test/vinyl/errinj_tx.result | 10 +- > test/vinyl/hermitage.result | 122 ++-- > test/vinyl/mvcc.result | 1066 +++++++++++++++---------------- > test/vinyl/mvcc.test.lua | 4 +- > test/vinyl/tx_conflict.result | 2 +- > test/vinyl/tx_conflict.test.lua | 2 +- > test/vinyl/tx_gap_lock.result | 189 +++--- > test/vinyl/tx_gap_lock.test.lua | 3 +- > test/vinyl/tx_serial.result | 2 +- > test/vinyl/tx_serial.test.lua | 2 +- > third_party/lua-yaml/lyaml.cc | 22 +- > 17 files changed, 747 insertions(+), 739 deletions(-) > > diff --git a/test/vinyl/mvcc.result b/test/vinyl/mvcc.result > index 1941744b9..db7fc8e83 100644 > --- a/test/vinyl/mvcc.result > +++ b/test/vinyl/mvcc.result > @@ -41,29 +41,29 @@ t = box.space.test > -- > c1:begin() > --- > -- > +- null How about to start returning nothing instead of returning null so as to do not change the tests (or at least make the diff smaller)? I see, that most of the diff is from txn_proxy, which always does return 'something'. You can change it so as to do not just return, but check if a result is not null, and only then return. Otherwise do nothing or empty return. I am sure it will work since space:get(), for example, still can return nothing (!= null), and this is why other tests didn't fail.
next prev parent reply other threads:[~2019-01-24 21:27 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-22 2:12 [tarantool-patches] [PATCH v2 0/3] lua-yaml null/boolean fixes Alexander Turenko 2019-01-22 2:12 ` [tarantool-patches] [PATCH v2 1/3] lua-yaml: verify arguments count Alexander Turenko 2019-01-24 21:26 ` [tarantool-patches] " Vladislav Shpilevoy 2019-02-05 3:29 ` Alexander Turenko 2019-02-05 19:36 ` Vladislav Shpilevoy 2019-02-11 13:32 ` Alexander Turenko 2019-02-15 21:28 ` Vladislav Shpilevoy 2019-01-22 2:12 ` [tarantool-patches] [PATCH v2 2/3] lua-yaml: fix boolean/null representation in yaml Alexander Turenko 2019-01-24 21:26 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-24 21:32 ` Vladislav Shpilevoy 2019-02-05 3:29 ` Alexander Turenko 2019-02-05 19:36 ` Vladislav Shpilevoy 2019-02-15 21:06 ` Vladislav Shpilevoy 2019-02-15 21:23 ` Alexander Turenko 2019-02-18 18:55 ` Alexander Turenko 2019-02-22 15:14 ` Vladislav Shpilevoy 2019-01-22 2:12 ` [tarantool-patches] [PATCH v2 3/3] lua-yaml: treat an empty document/value as null Alexander Turenko 2019-01-24 21:26 ` Vladislav Shpilevoy [this message] 2019-02-05 3:30 ` [tarantool-patches] " Alexander Turenko 2019-01-24 21:26 ` [tarantool-patches] Re: [PATCH v2 0/3] lua-yaml null/boolean fixes Vladislav Shpilevoy 2019-02-25 11:27 ` Kirill Yukhin 2019-03-05 16:40 ` Alexander Turenko 2019-03-06 7:21 ` 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=0a841ae0-f03f-5406-5a2e-d3fc81843784@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v2 3/3] lua-yaml: treat an empty document/value as null' \ /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