Openbravo Issue Tracking System - Retail Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0035776 | Retail Modules | StoreServer | public | 2017-04-12 16:13 | 2018-03-13 19:10 |
| Reporter | plujan | ||||
| Assigned To | mtaal | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | out of date | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | main | ||||
| 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 | 0035776: [RR17Q2] Error in the console while an automatic incremental is loading | ||||
| Description | In a Multi Server environment, when the automatic incremental refresh has been configured to launch often, I've seen in the log an error message: "The logic should not get to this line org.openbravo.retail.posterminal.master.BPLocation" | ||||
| Steps To Reproduce | 1. Get the incremental refresh to be launched every 10 minutes 2. Log in the webPOS and wait in the main page by 10 minutes 3. A message saying that if you do not do anything it will relaunch will be shown. 4. A reload of the context is triggered. In the js console, there is an error message "The logic should not get to this line org.openbravo.retail.posterminal.master.BPLocation" while loading the business partner location table. | ||||
| Proposed Solution | This is the commit related with this error: https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/rev/a17e34ee0e87 [^] In a formal sense it should be considered a regression, since the message was not being shown before although the functional path was being executed. In case console errors like this were intended to be released (ie it is not developers' debug code), I suggest to add some more descriptive message since end users will be seeing it. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2017-04-12 16:13 | plujan | New Issue | |||
| 2017-04-12 16:13 | plujan | Assigned To | => mtaal | ||
| 2017-04-12 16:13 | plujan | Triggers an Emergency Pack | => No | ||
| 2017-06-26 12:04 | mtaal | Status | new => closed | ||
| 2017-06-26 12:04 | mtaal | Resolution | open => unable to reproduce | ||
| 2017-06-26 15:45 | mtaal | Note Added: 0097668 | |||
| 2017-06-26 15:45 | mtaal | Status | closed => new | ||
| 2017-06-26 15:45 | mtaal | Resolution | unable to reproduce => open | ||
| 2018-03-13 19:10 | mtaal | Status | new => closed | ||
| 2018-03-13 19:10 | mtaal | Resolution | open => out of date | ||
| Notes | |||||
|
|
|||||
|
|
||||