-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.1.3
-
Component/s: Test Framework
-
Tags:
-
Team:PLATFORM
-
Sprint:UI - 2023-6
-
Story Points:2
Since the upgrade of the nuxeo-js-client to 4.0.3, the vocabularies fixture has the following issue at teardown:
[2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] TypeError: opts.schemas is not iterable [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] TypeError: opts.schemas is not iterable [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at Request._computeOptions (/home/jenkins/workspace/retention_nuxeo-retention_PR-106/nuxeo-retention-web/node_modules/nuxeo/lib/base.js:244:34) [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at Request.execute (/home/jenkins/workspace/retention_nuxeo-retention_PR-106/nuxeo-retention-web/node_modules/nuxeo/lib/request.js:121:26) [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at Request.delete (/home/jenkins/workspace/retention_nuxeo-retention_PR-106/nuxeo-retention-web/node_modules/nuxeo/lib/request.js:111:17) [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at map (/home/jenkins/workspace/retention_nuxeo-retention_PR-106/nuxeo-retention-web/node_modules/@nuxeo/nuxeo-web-ui-ftest/features/step_definitions/support/fixtures/vocabularies.js:33:16) [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at Array.map (<anonymous>) [2023-03-30T02:00:12.938Z] [chrome 110.0.5481.77 Linux #0-2] at World.<anonymous> (/home/jenkins/workspace/retention_nuxeo-retention_PR-106/nuxeo-retention-web/node_modules/@nuxeo/nuxeo-web-ui-ftest/features/step_definitions/support/fixtures/vocabularies.js:30:28)
The issue has been observed in the nuxeo-retention addon ftests.
The problem is that at teardown the fixture is giving the directory entry to the delete method whereas it should give only the id as path.
The problem was already present in previous version, but it was hidden by another issue which happened on directory entry creation, which has been fixed in the recent nuxeo-js-client version.
For the record, the directory entry was created on nuxeo, but it seems that the unmarshalling was failing with the error below, and then silently caught:
TypeError: Cannot read property '_nuxeo' of undefined
- clones
-
-
- Resolved
-
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
