Skip to content

Handle websocket error gracefully + add retry logic (#149) #252

Handle websocket error gracefully + add retry logic (#149)

Handle websocket error gracefully + add retry logic (#149) #252

Re-run triggered October 7, 2025 16:26
Status Failure
Total duration 1m 9s
Artifacts 1

release.yml

on: push
Charts release
Charts release
Is release?
13s
Is release?
Repository changes
18s
Repository changes
Build Docker Image
6m 30s
Build Docker Image
Build E2B template
8m 33s
Build E2B template
Python Tests  /  Python SDK - Build and test
32s
Python Tests / Python SDK - Build and test
JS Tests  /  JS SDK - Build and test
51s
JS Tests / JS SDK - Build and test
Release
0s
Release
Code Interpreter Release Failed - Slack Notification
8s
Code Interpreter Release Failed - Slack Notification
Fit to window
Zoom out
Zoom in

Annotations

10 errors
tests/defaultKernels.test.ts > test top-level await and promise resolution: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"itm0lodz4wm033jmmg4w6","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/defaultKernels.test.ts:28:20
tests/defaultKernels.test.ts > test esm imports: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"ikdj9eue96ikxxv9219jm","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/defaultKernels.test.ts:13:18
tests/defaultKernels.test.ts > test js kernel: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"i4ei006lkejga7ld5gss5","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/defaultKernels.test.ts:6:18
tests/data.test.ts > get data: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"iawbxylv31hvey82xlcnh","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/data.test.ts:6:21
tests/callbacks.test.ts > callback stderr: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"iwiwxw1ibjqvx6lbtb875","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/callbacks.test.ts:37:18
tests/callbacks.test.ts > callback stdout: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"iy4zd7k7i59lbpyaqyetg","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/callbacks.test.ts:27:18
tests/callbacks.test.ts > callback error: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"ikoqwwlq9fwb9jk1ugeba","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/callbacks.test.ts:17:18
tests/callbacks.test.ts > callback results: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"ixin82tdfj89ekq6q7g27","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/callbacks.test.ts:7:18
tests/basic.test.ts > basic: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"ipgjbhzan3pfo81jsvs7g","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/basic.test.ts:6:18
tests/bash.test.ts > bash: js/src/messaging.ts#L11
TimeoutError: {"sandboxId":"iv9eheh7pq8olqoltryrn","message":"The sandbox is running but port is not open","port":49999,"code":502}: This error is likely due to sandbox timeout. You can modify the sandbox timeout by passing 'timeoutMs' when starting the sandbox or calling '.setTimeout' on the sandbox with the desired timeout. ❯ extractError src/messaging.ts:11:14 ❯ Sandbox.runCode src/sandbox.ts:244:21 ❯ tests/bash.test.ts:7:18