From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH 0/3] Credentials follow up Date: Thu, 31 Oct 2019 22:42:31 +0100 [thread overview] Message-ID: <cover.1572558071.git.v.shpilevoy@tarantool.org> (raw) The patchset fixes a flaky test, a C++ exception thrown in C, and invalid memory access problem left after the patch making struct credentials a complex object with a constructor and a destructor. Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-4597-credentials-follow-up-2 Issue: https://github.com/tarantool/tarantool/issues/4597 Vladislav Shpilevoy (3): test: fix flaky box/access_sysview.test.lua user: don't throw C++ exception from user_find_by_name session: su left dangling credentials object on stack src/box/lua/session.c | 3 +-- src/box/user.cc | 2 +- test/box/access.result | 11 +++++++++++ test/box/access.test.lua | 6 ++++++ test/box/access_sysview.result | 2 +- test/box/access_sysview.test.lua | 2 +- 6 files changed, 21 insertions(+), 5 deletions(-) -- 2.21.0 (Apple Git-122.2)
next reply other threads:[~2019-10-31 21:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-31 21:42 Vladislav Shpilevoy [this message] 2019-10-31 21:42 ` [Tarantool-patches] [PATCH 1/3] test: fix flaky box/access_sysview.test.lua Vladislav Shpilevoy 2019-11-04 17:20 ` Konstantin Osipov 2019-10-31 21:42 ` [Tarantool-patches] [PATCH 2/3] user: don't throw C++ exception from user_find_by_name Vladislav Shpilevoy 2019-11-04 17:22 ` Konstantin Osipov 2019-11-05 9:44 ` Vladislav Shpilevoy 2019-10-31 21:42 ` [Tarantool-patches] [PATCH 3/3] session: su left dangling credentials object on stack Vladislav Shpilevoy 2019-11-04 17:23 ` Konstantin Osipov 2019-11-01 13:54 ` [Tarantool-patches] [PATCH 0/3] Credentials follow up Kirill Yukhin 2019-11-04 17:23 ` 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=cover.1572558071.git.v.shpilevoy@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/3] Credentials follow up' \ /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