From: Leonid Vasiliev <lvasiliev@tarantool.org>
To: alexander.turenko@tarantool.org
Cc: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH 0/2] First part of the expose box.error task
Date: Thu, 30 Jan 2020 19:42:35 +0300 [thread overview]
Message-ID: <cover.1580401020.git.lvasiliev@tarantool.org> (raw)
https://github.com/tarantool/tarantool/issues/4398
https://github.com/tarantool/tarantool/tree/lvasiliev/gh-4398-expose-error-module
The first part of the expose box.error task includes:
1) Lua backtrace has been added to errors of the box.error module
2) Custom error type has been added. It's allows to create a new
error type in applications where the custom type is a subtype of error.
The next parts of the expose box.error task will include:
1) Transparent marshalling through net.box
2) Lua wrappers for the box.error interface
(it has to look like a https://github.com/tarantool/errors)
Leonid Vasiliev (2):
error: Add a Lua backtrace to error
error: Add the custom error type
src/box/errcode.h | 1 +
src/box/error.cc | 45 ++++++++++++++++++
src/box/error.h | 24 ++++++++++
src/box/lua/error.cc | 99 ++++++++++++++++++++++++++++++---------
src/lib/core/diag.c | 1 +
src/lib/core/diag.h | 1 +
src/lib/core/exception.cc | 1 +
src/lua/error.c | 42 ++++++++++++++++-
src/lua/error.h | 3 ++
src/lua/error.lua | 46 +++++++++++++-----
test/app/fiber.result | 35 ++++++++++----
test/app/fiber.test.lua | 11 ++++-
test/box/misc.result | 51 +++++++++++++++++---
test/box/misc.test.lua | 19 +++++++-
14 files changed, 326 insertions(+), 53 deletions(-)
--
2.17.1
next reply other threads:[~2020-01-30 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 16:42 Leonid Vasiliev [this message]
2020-01-30 16:42 ` [Tarantool-patches] [PATCH 1/2] Add a Lua backtrace to error Leonid Vasiliev
2020-01-30 16:42 ` [Tarantool-patches] [PATCH 2/2] Add the custom error type Leonid Vasiliev
2020-01-31 7:43 ` Leonid Vasiliev
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.1580401020.git.lvasiliev@tarantool.org \
--to=lvasiliev@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH 0/2] First part of the expose box.error task' \
/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