Skip to content

Feat/highlight vertex #1645

Feat/highlight vertex

Feat/highlight vertex #1645

Triggered via pull request May 15, 2026 17:35
Status Failure
Total duration 7m 27s
Artifacts 1

test_pr.yml

on: pull_request
test  /  ...  /  js-config
15s
test / config / js-config
test  /  ...  /  prepare
15s
test / prepare / prepare
Matrix: test / test-repository / test-browser
Matrix: test / test-repository / test-desktop
Matrix: test / test-repository / test-extension
Matrix: test / test-repository / test-integration
Matrix: test / test-repository / test-node
Matrix: test / test-repository / test-pyinstaller
Matrix: test / test-repository / test-python
test  /  ...  /  test-cloud
0s
test / test-repository / test-cloud
test  /  ...  /  test-docker
0s
test / test-repository / test-docker
test  /  oxlint
15s
test / oxlint
test  /  ...  /  semantic-commit
13s
test / semantic-commit / semantic-commit
test  /  ...  /  release
test / release / release
Matrix: test / deploy-repository / release-desktop
Waiting for pending jobs
Matrix: test / deploy-repository / release-pyinstaller
Waiting for pending jobs
test  /  ...  /  build-docker
test / deploy-repository / release-docker / build-docker
test  /  ...  /  release-node
test / deploy-repository / release-node
test  /  ...  /  release-python
test / deploy-repository / release-python
test  /  ...  /  release-cloud
test / deploy-repository / release-cloud
Matrix: test / deploy-repository / release-extension
Waiting for pending jobs
test  /  ...  /  notify
test / deploy-repository / notify / notify
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 13 warnings
unicorn(consistent-function-scoping): app/stores/data.js#L72
Function `getMeshComponentsByType` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): app/stores/data.js#L38
Function `formatedMeshComponents` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): app/stores/data.js#L31
Function `refAllItems` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): app/stores/data.js#L24
Function `refItem` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): app/stores/data.js#L16
Function `item` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): internal/stores/data_style/model/common.js#L6
Function `bulkMutateComponentStylesPerComponent` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): internal/stores/data_style/model/common.js#L6
Function `mutateComponentStyles` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): internal/stores/data_style/model/common.js#L6
Function `mutateModelComponentTypeStyle` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): internal/stores/data_style/model/common.js#L6
Function `mutateComponentStyle` does not capture any variables from its parent scope
unicorn(consistent-function-scoping): app/stores/viewer.js#L128
Function `launch` does not capture any variables from its parent scope
test / prepare / prepare
Repository is in a detached HEAD state. git-auto-commit will likely handle this automatically. To avoid it, check out a branch using the ref option in actions/checkout.
test / test-repository / test-integration (ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test / test-repository / test-integration (windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
OpenGeodeWeb-Front-js-config Expired
251 Bytes
sha256:cf726e759d92447f3b09405b441b39615517c58ac00a29ecc08e6a36b30d577b