Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0049048 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| backport | [POS2] POS | major | have not tried | 2022-04-06 14:53 | 2022-06-07 22:37 | |||
| Reporter | jarmendariz | View Status | public | |||||
| Assigned To | jarmendariz | |||||||
| Priority | high | Resolution | fixed | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | TAP | |||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | jarmendariz | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0049048: Improve jest tests to make them compatible with Node 16 | |||||||
| Description | Some tests are passing with the current Node version (v14), but v16 introduces some changes that makes a few test fails. At the moment we only noticed two scenarios: 1- In ErrorHandler.test.js, the runtime exception message changed from - "Cannot read property 'b' of undefined" to "Cannot read properties of undefined (reading 'b') 2- Unhandled Promise rejection warning: Currently in v14 the following message appears: (node:539993) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode [^]). (rejection id: 2) (node:539993) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. Starting from v16, those warnings becomes errors, so it would be nice to fix them as soon as possible. | |||||||
| Steps To Reproduce | See description | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0138139) jarmendariz (developer) 2022-06-07 22:37 |
Fixed on MR: https://gitlab.com/obcustomers/AGAP/org.openbravo.core2/-/merge_requests/79 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-04-13 09:12 | jarmendariz | Type | defect => backport |
| 2022-04-13 09:12 | jarmendariz | Target Version | => TAP |
| 2022-06-07 22:37 | jarmendariz | Note Added: 0138139 | |
| 2022-06-07 22:37 | jarmendariz | Status | scheduled => resolved |
| 2022-06-07 22:37 | jarmendariz | Resolution | open => fixed |
| 2022-06-07 22:37 | jarmendariz | Review Assigned To | => jarmendariz |
| 2022-06-07 22:37 | jarmendariz | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |