From: Nikita Pettik <korablev@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 6/7] iproto: refactor error encoding with mpstream Date: Wed, 25 Mar 2020 01:42:25 +0000 [thread overview] Message-ID: <20200325014225.GE30598@tarantool.org> (raw) In-Reply-To: <8e5c5ce4-69a3-4a8b-cb4e-8071e89564e3@tarantool.org> On 23 Feb 18:44, Vladislav Shpilevoy wrote: > Thanks for the patch! > > See 2 comments below. > > On 19/02/2020 15:16, Nikita Pettik wrote: > > From: Kirill Shcherbatov <kshcherbatov@tarantool.org> > > > > +} > > + > > int > > iproto_reply_error(struct obuf *out, const struct error *e, uint64_t sync, > > uint32_t schema_version) > > { > > - uint32_t msg_len = strlen(e->errmsg); > > - uint32_t errcode = box_error_code(e); > > - > > - struct iproto_body_bin body = iproto_error_bin; > > char *header = (char *)obuf_alloc(out, IPROTO_HEADER_LEN); > > if (header == NULL) > > return -1; > > > > + /* The obuf-based stream has reserved area for header. */ > > 2. No, you reserved space for the header just a few lines above. > Mpstream does not know anything about headers. Didn't really get what you mean here, so just in case dropped this comment at all :) > > + bool is_error = false; > > + struct mpstream stream; > > + mpstream_init(&stream, out, obuf_reserve_cb, obuf_alloc_cb, > > + mpstream_error_handler, &is_error); > > + > > + uint32_t used = obuf_size(out); > > + mpstream_iproto_encode_error(&stream, e); > > + mpstream_flush(&stream); > > + > > + uint32_t errcode = box_error_code(e); > > iproto_header_encode(header, iproto_encode_error(errcode), sync, > > - schema_version, sizeof(body) + msg_len); > > - body.v_data_len = mp_bswap_u32(msg_len); > > + schema_version, obuf_size(out) - used); > > + > > /* Malformed packet appears to be a lesser evil than abort. */ > > - return obuf_dup(out, &body, sizeof(body)) != sizeof(body) || > > - obuf_dup(out, e->errmsg, msg_len) != msg_len ? -1 : 0; > > + return is_error; > > }
next prev parent reply other threads:[~2020-03-25 1:42 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-19 14:16 [Tarantool-patches] [PATCH 0/7] Stacked diagnostics area Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 1/7] box: rename diag_add_error to diag_set_error Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 2/7] box/error: introduce box.error.set() method Nikita Pettik 2020-02-19 14:26 ` Cyrill Gorcunov 2020-02-19 14:30 ` Nikita Pettik 2020-02-19 14:53 ` Cyrill Gorcunov 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 3/7] box/error: don't set error created via box.error.new to diag Nikita Pettik 2020-02-22 17:18 ` Vladislav Shpilevoy 2020-03-25 1:02 ` Nikita Pettik 2020-03-26 0:22 ` Vladislav Shpilevoy 2020-03-26 1:03 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 4/7] box: introduce stacked diagnostic area Nikita Pettik 2020-02-19 21:10 ` Vladislav Shpilevoy 2020-02-20 11:53 ` Nikita Pettik 2020-02-20 18:29 ` Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:34 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 5/7] box/error: clarify purpose of reference counting in struct error Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:40 ` Nikita Pettik 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 6/7] iproto: refactor error encoding with mpstream Nikita Pettik 2020-02-23 17:44 ` Vladislav Shpilevoy 2020-03-25 1:42 ` Nikita Pettik [this message] 2020-02-19 14:16 ` [Tarantool-patches] [PATCH 7/7] iproto: support error stacked diagnostic area Nikita Pettik 2020-02-23 17:43 ` Vladislav Shpilevoy 2020-03-25 1:38 ` Nikita Pettik 2020-02-22 17:18 ` [Tarantool-patches] [PATCH 0/7] Stacked diagnostics area 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=20200325014225.GE30598@tarantool.org \ --to=korablev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 6/7] iproto: refactor error encoding with mpstream' \ /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