From be6a140777b8cf5a2ccb7bf57e1a44bbcade5f0b Mon Sep 17 00:00:00 2001 From: Lagrang3 Date: Mon, 24 Feb 2025 09:26:47 +0100 Subject: [PATCH] libplugin: fix LOG_TRACE for plugins A log event LOG_TRACE submitted by a plugin was being logged as **BROKEN** by lightningd before this commit. Changelog-Fixed: plugins can now log events under the LOG_TRACE flag. Signed-off-by: Lagrang3 --- lightningd/plugin.c | 2 +- plugins/libplugin.c | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/lightningd/plugin.c b/lightningd/plugin.c index 1182fab22..b4a5f7f83 100644 --- a/lightningd/plugin.c +++ b/lightningd/plugin.c @@ -498,7 +498,7 @@ static const char *plugin_log_handle(struct plugin *plugin, || level == LOG_IO_OUT) { return tal_fmt(plugin, "Unknown log-level %.*s, valid values are " - "\"debug\", \"info\", \"warn\", or \"error\".", + "\"trace\", \"debug\", \"info\", \"warn\", or \"error\".", json_tok_full_len(leveltok), json_tok_full(plugin->buffer, leveltok)); } diff --git a/plugins/libplugin.c b/plugins/libplugin.c index 78fba478b..ce8176746 100644 --- a/plugins/libplugin.c +++ b/plugins/libplugin.c @@ -1835,7 +1835,8 @@ void plugin_logv(struct plugin *p, enum log_level l, json_object_start(js, "params"); json_add_string(js, "level", - l == LOG_DBG ? "debug" + l == LOG_TRACE ? "trace" + : l == LOG_DBG ? "debug" : l == LOG_INFORM ? "info" : l == LOG_UNUSUAL ? "warn" : l == LOG_TRACE ? "trace"