chore(deps): drop unused npm-check-updates devDep to clear tar alerts #461
mishushakovsdk_tests.yml
on: pull_request
Matrix: Staging / CLI Tests / test
Matrix: Production / CLI Tests / test
Matrix: Staging / JS SDK Tests / test
Matrix: Production / JS SDK Tests / test
Matrix: Staging / Python SDK Tests / test
Matrix: Production / Python SDK Tests / test
Annotations
22 errors and 12 warnings
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should throw VolumeError when writing to existing file with force: false:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should overwrite an existing file with force option:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read an empty file:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a file with blob format:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read binary data:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a file with bytes format:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a text file:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/sandbox/network.test.ts > deny all traffic using allTraffic helper > deny all traffic using allTraffic helper:
packages/js-sdk/tests/sandbox/network.test.ts#L82
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 301
+ date: Thu, 30 Apr 2026 17:12:32 GMT
+ location: https://one.one.one.one/
+ location: https://one.one.one.one/
+ server: cloudflare
+ cf-ray: 9f482c042acaa39e-SEA
+
+ ",
}
❯ tests/sandbox/network.test.ts:82:7
|
|
tests/sandbox/network.test.ts > deny specific IP address > deny specific IP address:
packages/js-sdk/tests/sandbox/network.test.ts#L53
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 302
+ x-content-type-options: nosniff
+ location: https://dns.google/
+ date: Thu, 30 Apr 2026 17:12:32 GMT
+ content-type: text/html; charset=UTF-8
+ server: HTTP server (unknown)
+ content-length: 216
+ x-xss-protection: 0
+ x-frame-options: SAMEORIGIN
+
+ ",
}
❯ tests/sandbox/network.test.ts:53:7
|
|
tests/sandbox/network.test.ts > allow only 1.1.1.1 > allow specific IP with deny all traffic:
packages/js-sdk/tests/sandbox/network.test.ts#L31
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 302
+ x-content-type-options: nosniff
+ location: https://dns.google/
+ date: Thu, 30 Apr 2026 17:12:31 GMT
+ content-type: text/html; charset=UTF-8
+ server: HTTP server (unknown)
+ content-length: 216
+ x-xss-protection: 0
+ x-frame-options: SAMEORIGIN
+
+ ",
}
❯ tests/sandbox/network.test.ts:31:7
|
|
Staging / Python SDK Tests / Python SDK - Build and test (ubuntu-22.04)
Process completed with exit code 1.
|
|
Staging / Python SDK Tests / Python SDK - Build and test (windows-latest)
Process completed with exit code 1.
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should throw VolumeError when writing to existing file with force: false:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should overwrite an existing file with force option:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read an empty file:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a file with blob format:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read binary data:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a file with bytes format:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/volume/file.test.ts > Volume File Operations > writeFile and readFile > should write and read a text file:
packages/js-sdk/src/api/index.ts#L44
VolumeError: 500: Error when creating directory
❯ handleApiError src/api/index.ts:44:10
❯ Function.create src/volume/index.ts:110:17
❯ test.extend.volume.auto tests/setup.ts:122:22
|
|
tests/sandbox/network.test.ts > deny all traffic using allTraffic helper > deny all traffic using allTraffic helper:
packages/js-sdk/tests/sandbox/network.test.ts#L82
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 301
+ date: Thu, 30 Apr 2026 17:15:48 GMT
+ location: https://one.one.one.one/
+ location: https://one.one.one.one/
+ server: cloudflare
+ cf-ray: 9f4830cacff9a37d-SEA
+
+ ",
}
❯ tests/sandbox/network.test.ts:82:7
|
|
tests/sandbox/network.test.ts > deny specific IP address > deny specific IP address:
packages/js-sdk/tests/sandbox/network.test.ts#L53
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 302
+ x-content-type-options: nosniff
+ location: https://dns.google/
+ date: Thu, 30 Apr 2026 17:15:47 GMT
+ content-type: text/html; charset=UTF-8
+ server: HTTP server (unknown)
+ content-length: 216
+ x-xss-protection: 0
+ x-frame-options: SAMEORIGIN
+
+ ",
}
❯ tests/sandbox/network.test.ts:53:7
|
|
tests/sandbox/network.test.ts > allow only 1.1.1.1 > allow specific IP with deny all traffic:
packages/js-sdk/tests/sandbox/network.test.ts#L31
AssertionError: promise resolved "{ exitCode: +0, error: undefined, …(2) }" instead of rejecting
- Expected
+ Received
- Error {
- "message": "rejected promise",
+ {
+ "error": undefined,
+ "exitCode": 0,
+ "stderr": "",
+ "stdout": "HTTP/2 302
+ x-content-type-options: nosniff
+ location: https://dns.google/
+ date: Thu, 30 Apr 2026 17:15:47 GMT
+ content-type: text/html; charset=UTF-8
+ server: HTTP server (unknown)
+ content-length: 216
+ x-xss-protection: 0
+ x-frame-options: SAMEORIGIN
+
+ ",
}
❯ tests/sandbox/network.test.ts:31:7
|
|
Production / CLI Tests / CLI - Build (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/checkout@v4, actions/setup-node@v3, pnpm/action-setup@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/
|
|
Staging / CLI Tests / CLI - Build (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/checkout@v4, actions/setup-node@v3, pnpm/action-setup@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/
|
|
Staging / CLI Tests / CLI - Build (windows-latest)
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-node@v3, pnpm/action-setup@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/
|
|
Production / CLI Tests / CLI - Build (windows-latest)
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-node@v3, pnpm/action-setup@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/
|
|
Staging / JS SDK Tests / JS SDK - Build and test (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/cache@v4, actions/checkout@v4, actions/setup-node@v3, pnpm/action-setup@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/
|
|
Production / JS SDK Tests / JS SDK - Build and test (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/cache@v4, actions/checkout@v4, actions/setup-node@v3, denoland/setup-deno@v1, pnpm/action-setup@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/
|
|
Production / Python SDK Tests / Python SDK - Build and test (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/checkout@v4, actions/setup-python@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/
|
|
Staging / Python SDK Tests / Python SDK - Build and test (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/checkout@v4, actions/setup-python@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/
|
|
Staging / Python SDK Tests / Python SDK - Build and test (windows-latest)
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@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/
|
|
Production / Python SDK Tests / Python SDK - Build and test (windows-latest)
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@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/
|
|
Staging / JS SDK Tests / JS SDK - Build and test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3, pnpm/action-setup@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/
|
|
Production / JS SDK Tests / JS SDK - Build and test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v3, denoland/setup-deno@v1, pnpm/action-setup@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/
|