View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010503 | Taler | wallet-core | public | 2025-10-17 11:42 | 2026-09-19 14:40 |
| Reporter | avalos | Assigned To | avalos | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | informing | Resolution | fixed | ||
| Target Version | 1.6 | Fixed in Version | 1.6 | ||
| Summary | 0010503: getDonationStatements should not require network [discussion] | ||||
| Description | I just found out that getDonationStatements does network calls to fetch information from the Donau. Since I'm using the request to render the statements in the main balances (assets) list, it is important that the request returns a list immediately. However, right now that Donau is down, it returns this error: 2025-10-17T11:20:09.039Z wallet.ts INFO finished wallet core request getDonauStatements with error: { "code": 7002, "when": { "t_ms": 1760700009038 }, "hint": "Error response did not even contain JSON. The request URL might be wrong or the service might be unavailable.", "requestUrl": "https://donau.test.taler.net/config", "requestMethod": "GET", "httpStatusCode": 504, "response": "<html>\r\n<head><title>504 Gateway Time-out</title></head>\r\n<body>\r\n<center><h1>504 Gateway Time-out</h1></center>\r\n<hr><center>nginx/1.26.3</center>\r\n</body>\r\n</html>\r\n", "contentType": "text/html" } | ||||
| Tags | No tags attached. | ||||
| It's not so easy: What if we have receipts that were not submitted yet? If we have network, it might make sense to try to submit them. Without network (or if the attempt to submit times out), we could serve the old statements, but possibly with a flag to indicate that they're outdated. But do we even need to ever show the statements when the DONAU is not reachable in the first place? | |
| I think we can resolve this as fixed, since the Android wallet balances screen is not affected anymore by a getDonationStatements taking longer to talk to the network. And getDonationStatements has a progress token now. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-10-17 11:42 | avalos | New Issue | |
| 2025-10-17 11:42 | avalos | Status | new => assigned |
| 2025-10-17 11:42 | avalos | Assigned To | => Florian Dold |
| 2025-10-17 14:53 | Florian Dold | Note Added: 0026191 | |
| 2025-10-17 14:54 | Florian Dold | Assigned To | Florian Dold => |
| 2025-10-17 14:54 | Florian Dold | Status | assigned => feedback |
| 2025-10-17 14:54 | Florian Dold | Summary | getDonationStatements should not require network => getDonationStatements should not require network [discussion] |
| 2026-07-28 20:30 | Florian Dold | Target Version | => 1.8 |
| 2026-09-11 17:23 | Florian Dold | Assigned To | => avalos |
| 2026-09-11 17:23 | Florian Dold | Status | feedback => informing |
| 2026-09-11 17:23 | Florian Dold | Resolution | open => fixed |
| 2026-09-11 17:23 | Florian Dold | Note Added: 0029961 | |
| 2026-09-19 14:38 | Christian Grothoff | Target Version | 1.8 => 1.6 |
| 2026-09-19 14:40 | Christian Grothoff | Fixed in Version | => 1.6 |