fix: enforce data isolation and harden shared servers in server mode #5397
asheshvAnnotations
15 errors and 16 warnings
|
run-python-tests-pg (macos-latest, 14)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 17)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 18)
Process completed with exit code 2.
|
|
run-python-tests-pg (windows-latest, 18)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 15)
Process completed with exit code 1.
|
|
run-python-tests-pg (windows-latest, 17)
Process completed with exit code 1.
|
|
run-python-tests-pg (macos-latest, 15)
Process completed with exit code 2.
|
|
run-python-tests-pg (windows-latest, 16)
Process completed with exit code 1.
|
|
run-python-tests-pg (ubuntu-22.04, 18)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 14)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 16)
Process completed with exit code 2.
|
|
run-python-tests-pg (macos-latest, 16)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 17)
Process completed with exit code 2.
|
|
run-python-tests-pg (ubuntu-22.04, 15)
Process completed with exit code 2.
|
|
run-python-tests-pg (windows-latest, 14)
Process completed with exit code 1.
|
|
run-python-tests-pg (macos-latest, 14)
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/upload-artifact@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/
|
|
run-python-tests-pg (macos-latest, 14)
postgresql@14 has been deprecated because it is not supported upstream! It will be disabled on 2026-11-12.
|
|
run-python-tests-pg (macos-latest, 17)
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/upload-artifact@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/
|
|
run-python-tests-pg (macos-latest, 18)
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/upload-artifact@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/
|
|
run-python-tests-pg (windows-latest, 18)
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/upload-artifact@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/
|
|
run-python-tests-pg (windows-latest, 15)
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/upload-artifact@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/
|
|
run-python-tests-pg (windows-latest, 17)
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/upload-artifact@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/
|
|
run-python-tests-pg (macos-latest, 15)
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/upload-artifact@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/
|
|
run-python-tests-pg (windows-latest, 16)
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/upload-artifact@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/
|
|
run-python-tests-pg (ubuntu-22.04, 18)
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/upload-artifact@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/
|
|
run-python-tests-pg (ubuntu-22.04, 14)
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/upload-artifact@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/
|
|
run-python-tests-pg (ubuntu-22.04, 16)
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/upload-artifact@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/
|
|
run-python-tests-pg (macos-latest, 16)
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/upload-artifact@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/
|
|
run-python-tests-pg (ubuntu-22.04, 17)
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/upload-artifact@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/
|
|
run-python-tests-pg (ubuntu-22.04, 15)
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/upload-artifact@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/
|
|
run-python-tests-pg (windows-latest, 14)
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/upload-artifact@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
regression-log-macos-latest-pg14
|
217 KB |
sha256:ff484529911497127f51dd844e24c018adc3dade8b6ed9d36a789ab5595b37a4
|
|
|
regression-log-macos-latest-pg15
|
215 KB |
sha256:6c97e2c06747d8a2dc7ffffe1dba8e1db6fca2c1ad6f8396e2bec2d6354db3b0
|
|
|
regression-log-macos-latest-pg16
|
213 KB |
sha256:acec3505f5ec6b0880a1001533c9848a8a45d1d120f3e507bd98762db42fe2de
|
|
|
regression-log-macos-latest-pg17
|
212 KB |
sha256:cf02787cad15090e8d8703903dcc9f601acb1aa25cdf72a6bd52072d6cfc5c8e
|
|
|
regression-log-macos-latest-pg18
|
225 KB |
sha256:e46b23719c8a04543c4b259eb72624e12c28ce145ba98529585d59fdb9b271cf
|
|
|
regression-log-ubuntu-22.04-pg14
|
238 KB |
sha256:4597e99656133180f0bdb6b3bac3a4b6b0ccc4d0e620f38962cdf70c72164777
|
|
|
regression-log-ubuntu-22.04-pg15
|
227 KB |
sha256:d13530c3825de2586cc23210a193a1db08af7eecf990e640b7fb5eb56da06514
|
|
|
regression-log-ubuntu-22.04-pg16
|
238 KB |
sha256:2e2abc2b572acb201b803e64e5194e4f21b8d3b666da403afe9ecfa0c142217a
|
|
|
regression-log-ubuntu-22.04-pg17
|
237 KB |
sha256:4b960c8b79ab31a07b4a200d013c23b911249e42b4721dfc0eae053c68e76fdb
|
|
|
regression-log-ubuntu-22.04-pg18
|
228 KB |
sha256:4aa8478ac46a4f9e21ecf5a9d188600218349288cd533c8079eebdf934a72cba
|
|
|
regression-log-windows-latest-pg14
|
204 KB |
sha256:67ff699c163c9b71f7defb373af3c934f4d762e76d0b35c7ae3f74132c5eadaf
|
|
|
regression-log-windows-latest-pg15
|
205 KB |
sha256:6ea514404f82ea6dc25ab87bf51317de178d6426f8b7ad132264c912bf833144
|
|
|
regression-log-windows-latest-pg16
|
204 KB |
sha256:6962b63ecd3bd80dff4221e619e44c8a75d7ba4575ab739c07ab5b369ba757e5
|
|
|
regression-log-windows-latest-pg17
|
206 KB |
sha256:d342dd23da7f678875e0d313e08a42b005b231570df20ac33230a3b9e2864ee5
|
|
|
regression-log-windows-latest-pg18
|
198 KB |
sha256:330dc1384af4f7594aba2ca4168b73e920a34b42c15a3f138f60dbfa4f186fd5
|
|
|
server-log-macos-latest-pg14
|
36.4 KB |
sha256:237fb0256b996f2a813611f31516d36ac71f9f8f9d00580bb12c56ef0b9ba92c
|
|
|
server-log-macos-latest-pg15
|
36.4 KB |
sha256:6aa83f837ffef55c4f2365add57f7967499529e567838ceae8fd5b52ab2b947e
|
|
|
server-log-macos-latest-pg16
|
36.2 KB |
sha256:2068322f6b0bba26e0001f265a15ded6801b4b4fdf90505169924cc055c81a33
|
|
|
server-log-macos-latest-pg17
|
36.2 KB |
sha256:65fabdb3930543b2c41694fd139d9c068358c38af27441ce8784617111c81e7a
|
|
|
server-log-macos-latest-pg18
|
36.7 KB |
sha256:435f3f8d2750e505ef21d7d3d0c1eb3d2ed757c6061571ac385bf3ce07e144f4
|
|
|
server-log-ubuntu-22.04-pg14
|
36.2 KB |
sha256:d61229b4ce07c16e0aca7713e87720bfc94008eedb15ad7468f1972bad04ef4c
|
|
|
server-log-ubuntu-22.04-pg15
|
35.8 KB |
sha256:c4898d2b14da5743fa01cae428f66dead537361c06f6334e5367d181f4c99ac7
|
|
|
server-log-ubuntu-22.04-pg16
|
36.3 KB |
sha256:64372b85e2bb57f0c5db6c5cd42800a8cff10a3f729674be6db534553d1ad815
|
|
|
server-log-ubuntu-22.04-pg17
|
36.2 KB |
sha256:ed3f39be9d351530bcb7674d12e108c5ede99ba0567c9cef6f742ade2dd5ed9e
|
|
|
server-log-ubuntu-22.04-pg18
|
35.9 KB |
sha256:eecd994e1fb4f5772da3ddf14be044c53f004e33612813a144b844aa61861a3a
|
|
|
server-log-windows-latest-pg14
|
33.5 KB |
sha256:7859e29badc320565f5d217d64aba1c020b54d29263a8d1d3a9fee99f8e4b1d5
|
|
|
server-log-windows-latest-pg15
|
33.3 KB |
sha256:3cd49a065b3e6d28bcb1ba20aa33e10b78791ffe74d99fd7e549dde25486d538
|
|
|
server-log-windows-latest-pg16
|
33.4 KB |
sha256:0914146f172be1ed2c0f29351301b016c834aa9b1505a23f01e2489c3cbe758f
|
|
|
server-log-windows-latest-pg17
|
33.5 KB |
sha256:b1b173725141040019eb26209764f1eb2a6c51599f6684a2a1acabef5ba9d37b
|
|
|
server-log-windows-latest-pg18
|
33.3 KB |
sha256:f0ec4db7d43ed85e00cc2db3d211f005a9fd59c63c9385ced2de621e65cf46be
|
|