Skip to content

Fix injected setup cell producing SyntaxError; keep more stderr conte… #541

Fix injected setup cell producing SyntaxError; keep more stderr conte…

Fix injected setup cell producing SyntaxError; keep more stderr conte… #541

Triggered via push May 16, 2026 17:11
Status Failure
Total duration 23m 35s
Artifacts

deploy.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 12 warnings
build
Process completed with exit code 1.
deploy
Error: No artifacts named "github-pages" were found for this workflow run. Ensure artifacts are uploaded with actions/upload-artifact@v4 or later.
deploy
Error: No artifacts named "github-pages" were found for this workflow run. Ensure artifacts are uploaded with actions/upload-artifact@v4 or later. at getArtifactMetadata (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/api-client.js:85:1) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/deployment.js:66:1) at main (/home/runner/work/_actions/actions/deploy-pages/v4/src/index.js:30:1)
deploy
Fetching artifact metadata failed. Is githubstatus.com reporting issues with API requests, Pages, or Actions? Please re-run the deployment at a later time.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, 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/
Notebook failure
rf/v0.1.1/transmission_line_reflection: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Notebook failure
rf/v0.1.1/superheterodyne_receiver: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Notebook failure
rf/v0.1.1/rf_mixer_downconversion: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Notebook failure
rf/v0.1.1/rf_amplifier_compression: True)
Notebook failure
pathsim/v0.22.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
Notebook failure
pathsim/v0.21.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
Notebook failure
pathsim/v0.20.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
Notebook failure
pathsim/v0.19.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
Notebook failure
pathsim/v0.18.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
Notebook failure
pathsim/v0.17.0/fmcw_radar: 1019 #update blocks at algebraic depth (no error control)
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@v4. 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/