View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007893 | Taler | wallet-core | public | 2023-07-26 16:44 | 2024-03-07 20:49 |
| Reporter | MarcS | Assigned To | Florian Dold | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.4 | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0007893: Expiring PeerPushCredit stays Pending for receiving device | ||||
| Description | When the set timeout expires after having scanned a P2P send, wallet-core on the receiving device doesn't transfer the transaction from pending to expired, but only adds an error: "code": 7005, "when": { "t_ms": 1690357721065 }, "hint": "Unexpected HTTP status 410 in response", "requestUrl": "https://exchange.demo.taler.net/purses/.../merge", "requestMethod": "POST", "httpStatusCode": 410, "errorResponse": { "code": 1026, "hint": "The purse has expired." } | ||||
| Steps To Reproduce | On the sending device, prepare a P2P send transaction with a short timeout (e.g. 3 min). Scan with the receiving device, then wait until the transactions expires. The sending device got it right and shows Status: Expired. On the receiving device, the status stays Pending. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-07-26 16:44 | MarcS | New Issue | |
| 2023-07-26 16:44 | MarcS | Status | new => assigned |
| 2023-07-26 16:44 | MarcS | Assigned To | => Florian Dold |
| 2024-01-09 16:47 | Florian Dold | Status | assigned => resolved |
| 2024-01-09 16:47 | Florian Dold | Resolution | open => fixed |
| 2024-01-09 16:47 | Florian Dold | Note Added: 0020839 | |
| 2024-02-10 23:31 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2024-03-07 20:49 | Christian Grothoff | Status | resolved => closed |
