View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005666 | Taler | obsolete component | public | 2019-03-22 19:18 | 2019-12-20 18:12 |
| Reporter | Florian Dold | Assigned To | Marcello Stanisci | 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 | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0005666: bank and wire plugin should support date-based transaction histories | ||||
| Description | Some banks do not support querying only the latest transaction after some other transaction. In fact, a transaction with an *earlier* date might be reported in a second transaction list query, which was not present in the first. In practice, a banking API could give us a transaction that happened 5 days ago only today, even if we already got transactions confirmed from yesterday. Unfortunately we *need* to support this kind of awfully designed API, since that is what some banks offer. In turn, both the bank and the wire plugin API (!!) should support this alternate interface, while *also* supporting the faster one based on monotonically increasing transaction numbers. In summary, the bank and wire plugin must support querying for transactions based on a date range. The wire plugins also must ignore if duplicated transactions are reported. | ||||
| Tags | No tags attached. | ||||
| The Python Bank implements such date-based histories: 4a131f632f936eb49adb7f608851. Will leave this open until fakebank does the same. | |
| This commit: 5c496633092de5ebccd43e, adds the "/history-range" API to the fakebank + testing library. Note that both the pybank and fakebank have tests for the new feature, but not "a lot". However, we'll have many occasions to test this API once the wirewatch will be able to speak to them, so I'm going to close this bug! | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-03-22 19:18 | Florian Dold | New Issue | |
| 2019-03-22 19:18 | Florian Dold | Status | new => assigned |
| 2019-03-22 19:18 | Florian Dold | Assigned To | => Marcello Stanisci |
| 2019-04-04 16:27 | Marcello Stanisci | Note Added: 0014258 | |
| 2019-04-10 17:08 | Marcello Stanisci | Note Added: 0014286 | |
| 2019-04-10 17:08 | Marcello Stanisci | Status | assigned => informing |
| 2019-04-10 17:08 | Marcello Stanisci | Resolution | open => fixed |
| 2019-04-10 18:51 | Christian Grothoff | Product Version | => git (master) |
| 2019-04-10 18:51 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2019-04-10 18:51 | Christian Grothoff | Target Version | => 0.6 |
| 2019-12-20 18:12 | Christian Grothoff | Status | informing => closed |
| 2022-08-23 18:26 | Christian Grothoff | Category | bank (demonstrator) => py bank (demonstrator, obsolete) |
| 2023-12-03 00:23 | Christian Grothoff | Category | py bank (demonstrator, obsolete) => obsolete componet |
| 2023-12-11 19:08 | Florian Dold | Category | obsolete componet => obsolete component |