View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005492 | Taler | merchant backend | public | 2018-11-29 12:44 | 2021-08-24 14:23 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | 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 | major | Reproducibility | have not tried |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.8 | Fixed in Version | 0.8 | ||
| Summary | 0005492: database inconsistency results in internal server error (2501/2705?) | ||||
| Description | Marcello suggests some "some discrepancy exists between db tables". The DB was reset, the backup is in demo-blue "talerdemo_db_dump.sql". To be investigated. | ||||
| Tags | No tags attached. | ||||
| Changing category, as the generated errors point to the merchant backend, not the exchange. | |
| 529cf92..828cd52 cleans up the /proposal logic improving error messages and proposal generation (nicer style), but also fixing a previously improperly done (lack of transaction scope) pre-flight test for an already existing order. Now the constraint check is simply done by relying on the DB constraint, and then we just run the 'get_order' to confirm that the hard error was indeed the constraint violation and not something else. So in the common case the result should be much faster, and we properly use the transactions now. It is _not_ clear that this was the bug, though. | |
| 84d4c87..9b683b2 improves logging in case this bug reappears. | |
| Unassigning, as I am not sure how to reproduce (loaded the DB, but would need a matching frontend setup to generate failing transactions). Hopefully the new logging will help diagnose this if this is still an issue. | |
| Merchant backend and database schema have changed completely. No point in even trying to reproduce this issue at this point. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-11-29 12:44 | Christian Grothoff | New Issue | |
| 2018-11-29 12:44 | Christian Grothoff | Status | new => assigned |
| 2018-11-29 12:44 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2019-01-08 18:12 | Christian Grothoff | Priority | normal => urgent |
| 2019-01-10 13:12 | Christian Grothoff | Category | exchange => mechant backend |
| 2019-01-10 13:12 | Christian Grothoff | Note Added: 0013451 | |
| 2019-01-10 14:25 | Christian Grothoff | Note Added: 0013452 | |
| 2019-01-10 14:34 | Christian Grothoff | Note Added: 0013453 | |
| 2019-01-10 14:35 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2019-01-10 14:35 | Christian Grothoff | Priority | urgent => normal |
| 2019-01-10 14:35 | Christian Grothoff | Note Added: 0013454 | |
| 2019-01-10 14:36 | Christian Grothoff | Status | assigned => feedback |
| 2020-08-28 22:01 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2020-08-28 22:01 | Christian Grothoff | Status | feedback => informing |
| 2020-08-28 22:01 | Christian Grothoff | Resolution | open => unable to reproduce |
| 2020-08-28 22:01 | Christian Grothoff | Fixed in Version | => 0.8 |
| 2020-08-28 22:01 | Christian Grothoff | Note Added: 0016794 | |
| 2020-08-28 22:01 | Christian Grothoff | Target Version | => 0.8 |
| 2021-08-24 14:23 | Christian Grothoff | Status | informing => closed |
| 2025-03-22 13:09 | Christian Grothoff | Category | mechant backend => merchant backend |