View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008775 | Taler | wallet-core | public | 2024-04-29 11:02 | 2025-04-17 21:52 |
| Reporter | Florian Dold | Assigned To | 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 | low | Severity | tweak | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0008775: consider allowing all non-final wallet-core states to be suspended/resumed | ||||
| Description | This change to the state machine reflects what the implementation does and would make it overall simpler and clearer. The current state machine doesn't allow dialog states to be suspended. But dialog states can indeed do network activity (to check for expiration, check if another wallet completed the transaction, ...) so they should be suspendable. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-29 11:02 | Florian Dold | New Issue | |
| 2024-04-29 11:02 | Florian Dold | Status | new => assigned |
| 2024-04-29 11:02 | Florian Dold | Assigned To | => Florian Dold |
| 2024-04-29 11:03 | Florian Dold | Description Updated | |
| 2024-07-31 16:38 | Florian Dold | Target Version | 0.14 => 1.0 stretch goals |
| 2024-07-31 16:38 | Florian Dold | Target Version | 1.0 stretch goals => post-1.0 |
| 2025-04-17 21:52 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-04-17 21:52 | Christian Grothoff | Status | assigned => acknowledged |