BE-587, BE-588: HashQL: Introduce CodeGenerationContext/CodeExecutionContext split and eval-stage Interner
#31996
test.yml
on: pull_request
setup
34s
Optimize CI
5s
Matrix: Publish
Matrix: Unit
Matrix: Integration
Tests passed
7s
Annotations
15 warnings and 26 notices
|
Optimize CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: withgraphite/graphite-ci-action@ee395f3a78254c006d11339669c6cabddf196f72. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
setup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-syntax-jexpr)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@local/hash-backend-utils)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-compiletest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@local/hash-isomorphic-utils)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@apps/hash-api)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@local/hash-graph-sdk)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@apps/hash-ai-worker-ts)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-hir)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-ast)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-eval)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hash-graph-api)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-mir)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Unit (@rust/hashql-core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5, mozilla-actions/***-action@7d986dd989559c6ecdb630a3fd2557667be217ad, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
sccache stats
100% - 127 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-syntax-jexpr)
*** server started successfully on port 4226
|
|
sccache stats
100% - 91 hits, 0 misses, 0 errors
|
|
Unit (@local/hash-backend-utils)
*** server started successfully on port 4226
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-compiletest)
*** server started successfully on port 4226
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
Unit (@local/hash-isomorphic-utils)
*** server started successfully on port 4226
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
Unit (@apps/hash-api)
*** server started successfully on port 4226
|
|
sccache stats
100% - 186 hits, 0 misses, 0 errors
|
|
Unit (@local/hash-graph-sdk)
*** server started successfully on port 4226
|
|
sccache stats
100% - 95 hits, 0 misses, 0 errors
|
|
Unit (@apps/hash-ai-worker-ts)
*** server started successfully on port 4226
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-hir)
*** server started successfully on port 4226
|
|
sccache stats
100% - 443 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-ast)
*** server started successfully on port 4226
|
|
sccache stats
100% - 492 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-eval)
*** server started successfully on port 4226
|
|
sccache stats
100% - 1406 hits, 0 misses, 0 errors
|
|
Unit (@rust/hash-graph-api)
*** server started successfully on port 4226
|
|
sccache stats
0% - 0 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-mir)
*** server started successfully on port 4226
|
|
sccache stats
100% - 148 hits, 0 misses, 0 errors
|
|
Unit (@rust/hashql-core)
*** server started successfully on port 4226
|