release 1.21.0: amount ladder classic + max-search
Generic currency ladder (check_amount_ladder.sh; goa-ladder shim). Default remains classic 23-rung withdraw/pay. New max-ladder mode hunts highest withdrawable amount with alt_unit_names in logs/report. Fixes force-select extract (external ladder_extract_rpubs.py; no stdin return SyntaxError), soft CEILING_REJECT on mint 5110/P0001, force-select 409 tries next rpub, pay SKIP_BALANCE when over available, and crash-proof report formatting. Verified live GOA: force-select 200, confirm 204, OK_BANK, report finishes without Traceback.
This commit is contained in:
parent
80643e6b3f
commit
32ffb6cdb1
10 changed files with 1952 additions and 1421 deletions
|
|
@ -9,7 +9,7 @@ Companions:
|
|||
- Android GUI → [`android-test/GUI-AUTOMATION-NOTES.md`](./android-test/GUI-AUTOMATION-NOTES.md)
|
||||
- Git / suite tree → [`VERSIONS.md`](./VERSIONS.md)
|
||||
|
||||
Scripts: `check_e2e.sh`, `check_goa_ladder.sh`, `taler-monitoring.sh`.
|
||||
Scripts: `check_e2e.sh`, `check_amount_ladder.sh` (compat `check_goa_ladder.sh`), `taler-monitoring.sh`.
|
||||
|
||||
Legend:
|
||||
|
||||
|
|
@ -67,6 +67,16 @@ Legend:
|
|||
| **Workaround** | Use `LADDER_STEPS≥5` (or higher) so random mids exist; treat zero / absolute-max / max-1-5110 as probes (soft `CEILING_REJECT` in mon ≥1.20.2). |
|
||||
| **Wanted** | Ladder plan docs: pin vs mid semantics; CLI structured error for amount-too-large / zero. |
|
||||
|
||||
### 3b. Higher withdraw amounts often fail at mint
|
||||
|
||||
| | |
|
||||
|--|--|
|
||||
| **Seen** | Classic GOA ladder high/random mids and ceiling pins — e.g. `GOA:747827072844319` → `FAIL_MINT` / `STOPPED … mint HTTP 500 { code :5110, … P0001 }`; same class of error on max / max-1. |
|
||||
| **Area** | **bank** / **ops** |
|
||||
| **Problem** | **Larger amounts** frequently hit bank/libeufin limits (HTTP 500, Taler **5110**, SQL **P0001**). Not specific to pin:max only — mid-high ladder steps fail the same way. Do not treat as wallet/`reserve_pub` when mint never succeeded. |
|
||||
| **Workaround** | Expect failures above some live ceiling; use max-search / soft ceiling handling; keep mid-range rungs for real withdraw/confirm tests. |
|
||||
| **Wanted** | Clear amount-too-large from bank (not opaque SQL 500); mon reports ceiling separately from hard fails. |
|
||||
|
||||
---
|
||||
|
||||
## 4. Exchange not auto-known for bank deep links / withdraw URIs
|
||||
|
|
@ -277,6 +287,8 @@ If only a few changes land, these unlock the most automation:
|
|||
| ladder explorer | `read_secret` / EXP_PW_FILE |
|
||||
| stage maxima | bank `max_wire` + keys min denom |
|
||||
| force-select | multi-rpub try; soft-skip confirm; empty scrape → WARN not balance fail |
|
||||
| higher amounts | mint 5110/P0001 common above live ceiling (§3b); classic soft `CEILING_REJECT`; max-ladder bounds hi; report uses alt_unit_names (Tera-GOA …) |
|
||||
| pay vs balance | never order more than wallet **available** (soft `SKIP_BALANCE`); pendingIncoming does not count as spendable |
|
||||
| wallet-db path | Prefer `*.sqlite3` (never `*.json` as db path) |
|
||||
| helper / python | mon PATH must include helper + python≥3.11 |
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue