Openbravo Issue Tracking System - POS2 |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0056377 | POS2 | Core | public | 2024-09-05 11:56 | 2024-11-12 23:44 |
|
| Reporter | AugustoMauch | |
| Assigned To | AugustoMauch | |
| Priority | normal | Severity | critical | Reproducibility | have not tried |
| Status | scheduled | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0056377: Management of inconsistent application state should be properly addressed in core2 applications |
| Description | From time to time, the application state gets inconsistent, apparently not reflecting the current state of the application but a previous one.
We looking for those inconsistencies on a case-to-case basis, and introducing mitigation measures on a case-to-case basis as well.
This mechanism should be improved, so that if any inconsistency is found, all the application state modules should be re-initialized properly. |
| Steps To Reproduce | - |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | feature request | 0056730 | | scheduled | ranjith_qualiantech_com | POS2 | Management of inconsistent application state should be properly addressed in EnyoPOS | | related to | feature request | 0054707 | | new | AugustoMauch | Retail Modules | Add support to select the state persistence method (localstorage vs indexed db) | | related to | defect | 0054743 | | closed | sreehari | Retail Modules | When the state persistence fails, the information of the cashup becomes outdated, and this can lead to data corruption | | related to | defect | 0056263 | | closed | ranjith_qualiantech_com | Retail Modules | Mitigation https://issues.openbravo.com/view.php?id=52070 [^] should not create a new cashup in POS | | related to | backport | 0052070 | 23Q2 | closed | meriem_azaf | POS2 | Cashup mitigation: do not check if current cashup is the last one processed, just check if it is processed | | related to | defect | 0056246 | | closed | sreehari | POS2 | Implement second Mitigation for duplicating document sequence number |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-09-05 11:56 | AugustoMauch | New Issue | |
| 2024-09-05 11:56 | AugustoMauch | Assigned To | => AugustoMauch |
| 2024-09-05 11:56 | AugustoMauch | Triggers an Emergency Pack | => No |
| 2024-09-05 12:03 | AugustoMauch | Status | new => scheduled |
| 2024-09-17 09:23 | Practics | Issue Monitored: Practics | |
| 2024-10-06 12:55 | hgbot | Note Added: 0170023 | |
| 2024-10-06 12:57 | hgbot | Note Added: 0170024 | |
| 2024-10-06 13:00 | hgbot | Note Added: 0170025 | |
| 2024-10-10 11:51 | AugustoMauch | Summary | Management of inconsistent application state should be properly addressed => Management of inconsistent application state should be properly addressed in core2 applications |
| 2024-10-10 11:52 | AugustoMauch | Issue cloned | 0056730 |
| 2024-10-10 11:55 | AugustoMauch | Relationship added | related to 0056730 |
| 2024-10-10 13:26 | eugeni | Issue Monitored: eugeni | |
| 2024-10-31 13:04 | malsasua | Relationship added | related to 0054707 |
| 2024-10-31 13:10 | malsasua | Relationship added | related to 0054743 |
| 2024-10-31 13:10 | malsasua | Relationship added | related to 0056263 |
| 2024-10-31 13:11 | malsasua | Relationship added | related to 0052070 |
| 2024-10-31 13:17 | malsasua | Relationship added | related to 0056246 |
| 2024-11-12 23:44 | hgbot | Note Added: 0171833 | |