View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003963 | Taler | wallet (WebExtension) | public | 2015-09-04 16:26 | 2019-12-26 20:37 |
| Reporter | Marcello Stanisci | 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 | 0.0 | ||||
| Target Version | 0.0 | ||||
| Summary | 0003963: reserve's polling starts too early | ||||
| Description | The current behaviour is to start the polling of a new reserve when the user clicks on the 'close' button of the dialog which gets open at reserve creation time. That way, the polling starts before the user has the time to actually wire the funds to the new reserve, resulting in an error of the type "no funds in reserve". | ||||
| Tags | No tags attached. | ||||
| child of | 0003955 | closed | Marcello Stanisci | adapt 'create reserve' to real world use cases |
| Well, it's not strictly false to 'start' polling at that time, but the 'no funds in reserve' error shouldn't be a "hard" error (and probably not even shown to the user by default). We should, however, think about having a 'log' where you record such interactions with the mint in a DB. | |
| As of now, the 'reserve' table has a 'last_fetch' column for each created (or attempted) reserve, which of course doesn't account for all the history of wallet-mint interactions. According to your comment, you suggest of having also a dedicated table accounting for all interactions with the mint. The problem here could be that such a table needs some extra care for preserving performance, since it is likely to grow fast and big. Any observations? | |
| The 'fix' now (in order to prioritize 0003961) is just to wait 10 seconds and then do the usual check. This issue calls for some finer 'heuristic' for checking the reserve, and for problems like showing or not some progress meter to the user.. and how to deal with (and notify to the user) the various errors that may occur while creating a reserve. | |
| solution mentioned in message 0009616, though that would work only on the demonstrator. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-09-04 16:26 | Marcello Stanisci | New Issue | |
| 2015-09-04 16:26 | Marcello Stanisci | Status | new => assigned |
| 2015-09-04 16:26 | Marcello Stanisci | Assigned To | => Marcello Stanisci |
| 2015-09-04 16:26 | Marcello Stanisci | Relationship added | child of 0003955 |
| 2015-09-06 17:11 | Christian Grothoff | Note Added: 0009612 | |
| 2015-09-09 07:40 | Marcello Stanisci | Note Added: 0009614 | |
| 2015-09-09 10:26 | Marcello Stanisci | Note Added: 0009616 | |
| 2015-09-19 18:38 | Christian Grothoff | Product Version | => 0.0 |
| 2015-09-19 18:38 | Christian Grothoff | Target Version | => 0.1 |
| 2015-09-19 18:49 | Christian Grothoff | Target Version | 0.1 => 0.0 |
| 2015-09-29 15:03 | Marcello Stanisci | Note Added: 0009665 | |
| 2015-09-29 15:03 | Marcello Stanisci | Status | assigned => informing |
| 2015-09-29 15:03 | Marcello Stanisci | Resolution | open => fixed |
| 2015-10-01 21:18 | Christian Grothoff | Status | informing => closed |
| 2019-12-26 20:37 | Florian Dold | Category | wallet (browser-based) => wallet (WebExtensions) |
| 2023-04-13 18:37 | Florian Dold | Category | wallet (WebExtensions) => wallet (WebExtension) |