From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f193.google.com (mail-lj1-f193.google.com [209.85.208.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 7FDE242EF5C for ; Thu, 2 Jul 2020 12:50:58 +0300 (MSK) Received: by mail-lj1-f193.google.com with SMTP id z24so6156325ljn.8 for ; Thu, 02 Jul 2020 02:50:58 -0700 (PDT) From: Cyrill Gorcunov Date: Thu, 2 Jul 2020 12:50:51 +0300 Message-Id: <20200702095054.367131-1-gorcunov@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Tarantool-patches] [PATCH v3 0/3] log: allow json formatter in boottime logger List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: tml Cc: yaroslav.dynnikov@gmail.com For some reason we've disabled usage of json formatter in early logging since the commit 098324556. Lets allow it back. v2: - add early verification of options for cases like box.cfg{log="syslog:", log_format="json"} - extend test v3: - pass the whole cfg table into verify_option helper - use string.startswith helper in verify_format branch gorcunov/gh-5121-logger-boot-json-3 issue https://github.com/tarantool/tarantool/issues/5121 Cyrill Gorcunov (3): core/say: allow to use json in boot logger lua/log: allow to use json formatter early test: app-tap/logger -- test json in boottime logger src/box/lua/load_cfg.lua | 6 +++--- src/lib/core/say.c | 7 ++---- src/lua/log.lua | 42 +++++++++++++++++++++++++++--------- test/app-tap/logger.test.lua | 19 ++++++++++++---- 4 files changed, 52 insertions(+), 22 deletions(-) -- 2.26.2