From a19514bbd38d978213e0e4742b5400d194bcaec8 Mon Sep 17 00:00:00 2001 From: Josef 'Jeff' Sipek Date: Thu, 12 Nov 2020 13:49:49 -0500 Subject: [PATCH] lib: event-filter - Do not assert that there in no output on error When the input is a simple (but invalid) expression (e.g., a=b=c) the output variable may be set. This is perfectly fine. The assertion (and the associated failure) come from when event filter parsing was switched to the new filter syntax (fcba1d530737813de11d9d730d5db6496e2e574b). --- src/lib/event-filter.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/lib/event-filter.c b/src/lib/event-filter.c index 46882e0811..40a1406be7 100644 --- a/src/lib/event-filter.c +++ b/src/lib/event-filter.c @@ -134,7 +134,6 @@ int event_filter_parse(const char *str, struct event_filter *filter, filter->named_queries_only = filter->named_queries_only && state.has_event_name; } else if (ret != 0) { /* error */ - i_assert(state.output == NULL); i_assert(state.error != NULL); *error_r = state.error; -- 2.47.3