Skip to content

Validate explicit empty field overrides in attack executor #1069

Validate explicit empty field overrides in attack executor

Validate explicit empty field overrides in attack executor #1069

Re-run triggered April 9, 2026 10:29
Status Cancelled
Total duration 1m 11s
Artifacts

docker_build.yml

on: pull_request
Build Devcontainer
1m 4s
Build Devcontainer
Build Production (local)
0s
Build Production (local)
Build Production (PyPI)
0s
Build Production (PyPI)
Test Import (local)
0s
Test Import (local)
Test GUI (local)
0s
Test GUI (local)
Test Jupyter (local)
0s
Test Jupyter (local)
Test Import (PyPI)
0s
Test Import (PyPI)
Test GUI (PyPI)
0s
Test GUI (PyPI)
Test Jupyter (PyPI)
0s
Test Jupyter (PyPI)
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Build Devcontainer
Canceling since a higher priority waiting request for docker_build-validate-empty-field-overrides exists
Build Devcontainer
The operation was canceled.
docker_build
Canceling since a higher priority waiting request for docker_build-validate-empty-field-overrides exists
Build Devcontainer
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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/