Skip to content

fix: replace O(n²) string concatenation in readLines with array buffering #496

fix: replace O(n²) string concatenation in readLines with array buffering

fix: replace O(n²) string concatenation in readLines with array buffering #496

Triggered via pull request April 14, 2026 14:32
Status Failure
Total duration 4m 24s
Artifacts 1

pull_request.yml

on: pull_request
build-template  /  Build E2B Template
1m 16s
build-template / Build E2B Template
charts-tests  /  Chart Data Extractor - Build and test
34s
charts-tests / Chart Data Extractor - Build and test
js-sdk  /  JS SDK - Build and test
2m 5s
js-sdk / JS SDK - Build and test
python-sdk  /  Python SDK - Build and test
2m 43s
python-sdk / Python SDK - Build and test
performance-tests  /  Performance tests
1m 21s
performance-tests / Performance tests
cleanup-build-template  /  Cleanup Build Template
10s
cleanup-build-template / Cleanup Build Template
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
js-sdk / JS SDK - Build and test
Process completed with exit code 1.
tests/env_vars/java.test.ts > env vars per execution (java): js/tests/env_vars/java.test.ts#L29
Error: Test timed out in 30000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/env_vars/java.test.ts:29:1
tests/contexts.test.ts > create context (secure traffic): js/tests/contexts.test.ts#L65
Error: Test timed out in 30000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ tests/contexts.test.ts:65:33
python-sdk / Python SDK - Build and test
Process completed with exit code 2.
cleanup-build-template / Cleanup Build Template
Process completed with exit code 1.
charts-tests / Chart Data Extractor - Build and test
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 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/
build-template / Build E2B Template
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 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/
performance-tests / Performance tests
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/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/
js-sdk / JS SDK - Build and test
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@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/
python-sdk / Python SDK - Build and test
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 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
performance-plot-496
362 KB
sha256:49eea756f9c9953217c852d788a53c89e6dfeb8198f5df345fba6054dc218494