Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org
Cc: alexander.turenko@tarantool.org
Subject: [tarantool-patches] Re: [PATCH 0/4] Serializer bugs
Date: Mon, 9 Sep 2019 20:57:04 +0200	[thread overview]
Message-ID: <f80659b6-efcf-f25e-b4e8-1d873012d292@tarantool.org> (raw)
In-Reply-To: <cover.1567633062.git.v.shpilevoy@tarantool.org>

Sorry, too many changes from Kostja. I send v2 in a separate
thread.

On 04/09/2019 23:44, Vladislav Shpilevoy wrote:
> The patchset fixes several problems about JSON and msgpack serializers.
> 
> 1) msgpackffi didn't use msgpack serializer options;
> 2) tuple serializer either;
> 3) update of a serializer option was not reflected in its Lua representation;
> 4) during serialization too nested tables are silently cropped and there was no
>   way to prevent it.
> 
> The patchset depends on fix of #4366 provided by Kirill.
> 
> Also it was discovered, that msgpackffi does not care *all* options. Not only
> about max_depth. I am not sure if it is worth fixing here (or at all) though.
> 
> Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-4434-box-lua-msgpack-cfg
> Issue: https://github.com/tarantool/tarantool/issues/4434
> 
> Vladislav Shpilevoy (4):
>   app: serializers update now is reflected in Lua
>   msgpack: make msgpackffi use encode_max_depth option
>   tuple: use global msgpack serializer in Lua tuple
>   app: allow to raise an error on too nested tables
> 
>  src/box/lua/tuple.c                  | 32 +++++++++++++------
>  src/lua/msgpack.c                    |  4 +++
>  src/lua/msgpackffi.lua               |  6 ++--
>  src/lua/utils.c                      | 37 ++++++++++++----------
>  src/lua/utils.h                      | 15 +++++++++
>  test/app-tap/json.test.lua           |  3 +-
>  test/app-tap/lua/serializer_test.lua | 31 +++++++++++++++++++
>  test/app-tap/msgpack.test.lua        |  3 +-
>  test/app-tap/msgpackffi.test.lua     | 30 +++++++++++++++++-
>  test/box/tuple.result                | 46 ++++++++++++++++++++++++++++
>  test/box/tuple.test.lua              | 21 +++++++++++++
>  test/unit/luaT_tuple_new.c           |  2 +-
>  third_party/lua-cjson/lua_cjson.c    | 10 ++++--
>  13 files changed, 207 insertions(+), 33 deletions(-)
> 

      parent reply	other threads:[~2019-09-09 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 21:44 [tarantool-patches] " Vladislav Shpilevoy
2019-09-04 21:44 ` [tarantool-patches] [PATCH 1/4] app: serializers update now is reflected in Lua Vladislav Shpilevoy
2019-09-04 21:44 ` [tarantool-patches] [PATCH 2/4] msgpack: make msgpackffi use encode_max_depth option Vladislav Shpilevoy
2019-09-04 21:44 ` [tarantool-patches] [PATCH 3/4] tuple: use global msgpack serializer in Lua tuple Vladislav Shpilevoy
2019-09-08 15:02   ` [tarantool-patches] " Vladislav Shpilevoy
2019-09-04 21:44 ` [tarantool-patches] [PATCH 4/4] app: allow to raise an error on too nested tables Vladislav Shpilevoy
2019-09-09 18:57 ` Vladislav Shpilevoy [this message]

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=f80659b6-efcf-f25e-b4e8-1d873012d292@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 0/4] Serializer bugs' \
    /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