exchange

Base system with REST service to issue digital coins, run by the payment service provider
Log | Files | Refs | Submodules | README | LICENSE

commit c630487dfc249628016efcef210b5b37f102c855
parent 8c4bc1121a10b525460a1d7de0973670c1f290fa
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 16 Jan 2021 22:36:30 +0100

nah, also on internal server errors and anything I can imagine we should backoff, not just on timeout

Diffstat:
Msrc/lib/exchange_api_handle.c | 1-
1 file changed, 0 insertions(+), 1 deletion(-)

diff --git a/src/lib/exchange_api_handle.c b/src/lib/exchange_api_handle.c @@ -1103,7 +1103,6 @@ keys_completed_cb (void *cls, { case 0: free_keys_request (kr); - /* FIXME: Maybe we should only increment when we know it's a timeout? */ exchange->keys_error_count++; exchange->kr = NULL; GNUNET_assert (NULL == exchange->retry_task);