From: Oleg Babin <olegrok@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>,
tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH vshard 1/1] router: bucket_id_strcrc32 and bucket_id_mpcrc32
Date: Mon, 2 Mar 2020 11:10:48 +0300 [thread overview]
Message-ID: <ddd8aa66-b376-034c-fa0b-d4db26e6be61@tarantool.org> (raw)
In-Reply-To: <98c0554d-be84-578c-f8e9-d64b23d63623@tarantool.org>
Hi! Your tests fail on Tarantool 1.10:
[001] Test failed! Result content mismatch:
[001] --- unit/router.result Mon Mar 2 10:54:48 2020
[001] +++ unit/router.reject Mon Mar 2 11:02:21 2020
[001] @@ -75,7 +75,7 @@
[001] | - - string
[001] | - '1'
[001] | - 477
[001] - | - - ctype<struct 106>
[001] + | - - number
[001] | - 1
[001] | - 477
[001] | ...
Without taking this into account - patch LGTM.
On 29/02/2020 20:09, Vladislav Shpilevoy wrote:
> The aforementioned module won't print a warning only once. It will
> print all the errors again once a code reload happens, because
> 'local errors_issued = {}' will be called again on reload, and
> will clear 'errors_issued' table. But perhaps it was done
> intentionally.
>
> I made it the same way. Intentionally. In that case it will help
> user to replace all bucket_id() calls during reloads, and after each
> reload he will be able to validate whether the message is printed
> again anywhere.
I see nothing bad to print deprecation message after code reload again.
It doesn't lead to flood into logs as it's a manual action.
---
Oleg Babin
next prev parent reply other threads:[~2020-03-02 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 23:52 Vladislav Shpilevoy
2020-02-26 7:15 ` Oleg Babin
2020-02-27 0:22 ` Vladislav Shpilevoy
2020-02-27 10:12 ` Oleg Babin
2020-02-29 17:09 ` Vladislav Shpilevoy
2020-03-02 8:10 ` Oleg Babin [this message]
2020-03-02 21:06 ` Vladislav Shpilevoy
2020-02-26 8:20 ` Konstantin Osipov
2020-02-27 0:25 ` Vladislav Shpilevoy
2020-02-27 6:53 ` Konstantin Osipov
2020-02-29 17:10 ` Vladislav Shpilevoy
2020-03-01 16:52 ` 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=ddd8aa66-b376-034c-fa0b-d4db26e6be61@tarantool.org \
--to=olegrok@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH vshard 1/1] router: bucket_id_strcrc32 and bucket_id_mpcrc32' \
/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