commit e1c22e0a66614bb80c9cc3d9f934491963ed2a7e
parent 3860df1a7426c486f42463cf95811bbc247b5149
Author: Christian Grothoff <grothoff@gnunet.org>
Date: Sat, 11 Jul 2026 19:25:31 +0200
-bugfixes
Diffstat:
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/src/exchange/taler-exchange-aggregator.c b/src/exchange/taler-exchange-aggregator.c
@@ -1306,6 +1306,7 @@ run_shard (void *cls)
GNUNET_break (GNUNET_DB_STATUS_HARD_ERROR != qs);
global_ret = EXIT_FAILURE;
GNUNET_SCHEDULER_shutdown ();
+ GNUNET_free (s);
return;
}
GNUNET_log (GNUNET_ERROR_TYPE_INFO,
@@ -1335,6 +1336,7 @@ drain_kyc_alerts (void *cls)
{
GNUNET_log (GNUNET_ERROR_TYPE_ERROR,
"Failed to obtain database connection!\n");
+ GNUNET_free (au);
global_ret = EXIT_FAILURE;
GNUNET_SCHEDULER_shutdown ();
return;
@@ -1345,6 +1347,7 @@ drain_kyc_alerts (void *cls)
{
GNUNET_log (GNUNET_ERROR_TYPE_ERROR,
"Failed to start database transaction!\n");
+ GNUNET_free (au);
global_ret = EXIT_FAILURE;
GNUNET_SCHEDULER_shutdown ();
return;
diff --git a/src/exchange/taler-exchange-httpd_common_kyc.c b/src/exchange/taler-exchange-httpd_common_kyc.c
@@ -155,8 +155,14 @@ fallback_result_cb (void *cls,
GNUNET_log (GNUNET_ERROR_TYPE_INFO,
"Fallback completed (row %llu)\n",
(unsigned long long) requirement_row);
+ /* For the HTTP client, us running the fallback
+ should not become a visible failure, after all
+ the fallback should put the account back into
+ a "correct" state (even if that is a deny-all
+ or manual review). Hence we do not return an
+ error here. */
kat->cb (kat->cb_cls,
- TALER_EC_EXCHANGE_KYC_AML_PROGRAM_FAILURE,
+ TALER_EC_NONE,
NULL);
}
else