anastasis

commit 3e64524c3f8cc8925be378f44d91d7cf20fe30ec
parent 78682a2ffe20d65dd7140ace21790051c03f092e
Author: Florian Dold <dold@taler.net>
Date:   Tue,  8 Sep 2026 21:15:37 +0200

codespell: correct comments and allow currency variable names

Correct spelling in the policy upload and database migration comments.
Allow the local identifiers als and clen in the codespell dictionary.

Diffstat:
M
contrib/ci/jobs/0-codespell/dictionary.txt
 | 
2
++
M
src/backend/anastasis-httpd_policy-upload.c
 | 
4
++--
M
src/stasis/stasis-0003.sql
 | 
2
+-
M
src/stasis/stasis-0004.sql
 | 
2
+-

4 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/contrib/ci/jobs/0-codespell/dictionary.txt b/contrib/ci/jobs/0-codespell/dictionary.txt
@@ -10,6 +10,8 @@
 ect
 ECT
 # Local variable names.
+als
+clen
 dum
 fo
 pres
diff --git a/src/backend/anastasis-httpd_policy-upload.c b/src/backend/anastasis-httpd_policy-upload.c
@@ -1203,7 +1203,7 @@ AH_handler_policy_post (
       GNUNET_log (GNUNET_ERROR_TYPE_INFO,
                   "Storage request limit exceeded, requesting payment\n");
       /* This implies that a NEW payment is required, so the order we are
-         about to create must have a fresh ID.  Re-using the identifier the
+         about to create must have a fresh ID.  Reusing the identifier the
          client supplied would ask the merchant for an order that already
          exists, which would not be helpful. */
       GNUNET_CRYPTO_random_block (&puc->payment_identifier,
@@ -1214,7 +1214,7 @@ AH_handler_policy_post (
       GNUNET_log (GNUNET_ERROR_TYPE_INFO,
                   "Policy store operation requires payment\n");
       /* This again implies that a NEW payment is required, so the order we are
-         about to create must have a fresh ID.  Re-using the identifier the
+         about to create must have a fresh ID.  Reusing the identifier the
          client supplied would ask the merchant for an order that already
          exists, which would not be helpful. */
       GNUNET_CRYPTO_random_block (&puc->payment_identifier,
diff --git a/src/stasis/stasis-0003.sql b/src/stasis/stasis-0003.sql
@@ -27,7 +27,7 @@ SET search_path TO anastasis;
 -- it return the first one, it makes it return a hard error, i.e. the account
 -- can no longer use that identifier at all.  Nothing enforced the uniqueness
 -- the readers assume, and the backend could be talked into inserting a
--- duplicate by re-using a payment identifier for an order the merchant
+-- duplicate by reusing a payment identifier for an order the merchant
 -- answers idempotently.  The C side no longer does that; this index is what
 -- makes it impossible rather than merely unlikely.
 --
diff --git a/src/stasis/stasis-0004.sql b/src/stasis/stasis-0004.sql
@@ -52,7 +52,7 @@ COMMENT ON TYPE taler_amount_currency
 -- by any released version (the getters either did not select the column or
 -- selected it without binding a result), so no decision depends on the value
 -- being right, and the alternative -- a NULL currency -- would make them
--- unparseable rather than merely historical.
+-- unparsable rather than merely historical.
 ALTER TABLE anastasis_truth_payment
   ALTER COLUMN amount TYPE taler_amount_currency
   USING ROW((amount).val, (amount).frac, 'KUDOS')::taler_amount_currency;