The jest module cannot be found after the update due
to a wrong transformation:
07:46:39 yarn run v1.22.19
07:46:39 $ jest --updateSnapshot
07:46:39 ● Validation Error:
07:46:39
07:46:39 Module vue-jest in the transform option was not found.
07:46:39 <rootDir> is: /tmp/code
07:46:39
07:46:39 Configuration Documentation:
07:46:39 https://jestjs.io/docs/configuration
This commit fixes the transformation and points to the new
'@vue/vue3-jest'
Change-Id: If781a23155352d0e3275c064bbca92d17076dbad
The files were not updates since long time.
Now they are in line with the english version, but still not traslated
Change-Id: I0ff78c1a8576ab2ee5e50a6553be1da7b86c0dee
Last added languages cannot be selected in the CSC while
creating a new soundset.
The ones missing from the list are:
French
Portuguese Brazilian
Arabic
Dutch
Hebrew
Change-Id: I33ce57e38abfb824b85346cbd1446a0ae2337036
The subscriber administrator can now assign as CLI of each
seat all the aliases configured in the customer
and not only the ones assigned to the user itself.
Change-Id: Id9a06c62bd2512cb19b34181b3de0d2c2fb6ff09
ncos and ncos_set setup should be visible in the 'Block Outgoing'
section only if:
* profile is not assigned or profile is assigned and contains
the ncos and/or the ncos_set attribute
* the user is a PBX subscriber's admin
* the user is subscriber (admin or not) in a NOT PBX customer
Change-Id: I27e7061e8cec055eddfe487f21052a4df0399373
update browsers, selenium & dependencies and updated tests to
accomondate new syntax thats been a requirement since selenium 4.7
Change-Id: I8f1c15e2093aed0d8277e47bbfce19d6a4728a74
yarnpkg is no longer available in Debian/bookworm, while we already ship
a bundled yarnpkg. So use that bundled yarnpkg binary also within our
Docker related actions. Also see commit bd8a150825 and MT#55813 (and
related to MT#55391).
Use our yarn binary as /tmp/yarn within Docker (to have to maintain it
only at one place). While at it, switch Docker instructions from ADD to
COPY, quoting from
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#add-or-copy ->
Although ADD and COPY are functionally similar, generally speaking, COPY is preferred.
Also, run pip3 install with --break-system-packages, to address new
PEP 668 specific behavior of pip3, as present in Debian/bookworm:
| error: externally-managed-environment
|
| × This environment is externally managed
| ╰─> To install Python packages system-wide, try apt install
| python3-xyz, where xyz is the package you are trying to
| install.
|
| If you wish to install a non-Debian-packaged Python package,
| create a virtual environment using python3 -m venv path/to/venv.
| Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
| sure you have python3-full installed.
|
| If you wish to install a non-Debian packaged Python application,
| it may be easiest to use pipx install xyz, which will manage a
| virtual environment for you. Make sure you have pipx installed.
|
| See /usr/share/doc/python3.11/README.venv for more information.
|
| note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
| hint: See PEP 668 for the detailed specification.
Change-Id: I09774d137925891a5f40e5597c40f48594f41d6f