[taler-exchange] branch master updated: add missing 'run-until-done' and convert test-pay to new wallet API call

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository exchange.

The following commit(s) were added to refs/heads/master by this push:
     new d1232f02 add missing 'run-until-done' and convert test-pay to new 
wallet API call
d1232f02 is described below

commit d1232f02cc5f715e63b23d55fc056122edfa14be
Author: Florian Dold <florian.dold@gmail.com>
AuthorDate: Sat Aug 29 15:12:22 2020 +0530

    add missing 'run-until-done' and convert test-pay to new wallet API call
---
 src/auditor/generate-revoke-basedb.sh | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/src/auditor/generate-revoke-basedb.sh 
b/src/auditor/generate-revoke-basedb.sh
index 6a215425..0a8a8263 100755
--- a/src/auditor/generate-revoke-basedb.sh
+++ b/src/auditor/generate-revoke-basedb.sh
@@ -165,6 +165,7 @@ taler-wallet-cli --no-throttle --wallet-db=$WALLET_DB api 
'withdrawTestBalance'
     --arg EXCHANGE_URL $EXCHANGE_URL
   )"
 
+taler-wallet-cli --no-throttle --wallet-db=$WALLET_DB run-until-done
 
 export coins=$(taler-wallet-cli --wallet-db=$WALLET_DB advanced dump-coins)
 
@@ -312,9 +313,16 @@ done
 
 # Now we buy something, only the coins resulting from recoup+refresh will be
 # used, as other ones are suspended
-taler-wallet-cli $TIMETRAVEL --wallet-db=$WALLET_DB testing test-pay \
-                 -m $MERCHANT_URL -k sandbox \
-                 -a "TESTKUDOS:0.02" -s "bar"
+taler-wallet-cli --no-throttle --wallet-db=$WALLET_DB api 'testPay' \
+  "$(jq -n '
+    {
+      amount: "TESTKUDOS:0.02",
+      merchantApiKey: "sandbox",
+      merchantBaseUrl: $MERCHANT_URL,
+      summary: "bar",
+    }' \
+    --arg MERCHANT_URL $MERCHANT_URL
+  )"
 taler-wallet-cli $TIMETRAVEL --wallet-db=$WALLET_DB run-until-done
 
 echo "Bought something with refresh-recouped coin"

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.