View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010558 | Taler | Magnet Bank integration | public | 2025-11-06 19:21 | 2026-01-25 15:29 |
| Reporter | Antoine A | Assigned To | Antoine A | 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 | feature | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0010558: Store in-db sync cursor | ||||
| Description | Store the transaction history cursor in the database to reduce amount of HTTP calls | ||||
| Tags | Magnet, performance | ||||
| Waiting on Magnet Bank fixing their API | |
| I have a plan for doing this without any API change from Magnet Bank by using a day cursor. It will still be a bit wastefull as we will parse the same transaction a lot but only the ones for current day | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-06 19:21 | Antoine A | New Issue | |
| 2025-11-06 19:21 | Antoine A | Status | new => assigned |
| 2025-11-06 19:21 | Antoine A | Assigned To | => Antoine A |
| 2025-11-06 19:22 | Antoine A | Note Added: 0026335 | |
| 2025-12-07 10:01 | Christian Grothoff | Target Version | => 1.4 |
| 2025-12-21 20:57 | Christian Grothoff | Target Version | 1.4 => post-1.0 |
| 2025-12-21 20:57 | Christian Grothoff | Tag Attached: Magnet | |
| 2025-12-28 12:56 | Antoine A | Note Added: 0027192 | |
| 2026-01-25 15:29 | Christian Grothoff | Tag Attached: performance | |
| 2026-01-25 15:29 | Christian Grothoff | Status | assigned => implementing |