feat: add timeout type field to TimeoutException/TimeoutError

[MaxwellCalkin]

Summary

Fixes #463

TimeoutException (Python) and TimeoutError (JS) now expose a typed field that identifies which kind of timeout occurred, so users no longer need to parse error messages to distinguish sandbox, request, and execution timeouts.

Python SDK

• TimeoutException gains a timeout_type: str | None attribute.
• Set at every construction site: format_sandbox_timeout_exception -> "sandbox_timeout", format_request_timeout_error -> "request_timeout", format_execution_timeout_error -> "execution_timeout", and the inline Code.canceled / Code.deadline_exceeded handlers in rpc.py.

JS SDK

• TimeoutError gains a readonly timeoutType?: TimeoutType property.
• A new TimeoutType union type ("sandbox_timeout" | "request_timeout" | "execution_timeout") is exported from the package.
• Set at every construction site: formatSandboxTimeoutError, and the Code.Canceled / Code.DeadlineExceeded handlers in rpc.ts.

Usage

from e2b import AsyncSandbox, TimeoutException

try:
    sandbox = await AsyncSandbox.create()
    await sandbox.commands.run("sleep 999", timeout=1)
except TimeoutException as e:
    if e.timeout_type == "execution_timeout":
        print("Command took too long")
    elif e.timeout_type == "sandbox_timeout":
        print("Sandbox expired")

import { Sandbox, TimeoutError } from 'e2b'

try {
  const sandbox = await Sandbox.create('base')
  await sandbox.commands.run('sleep 999', { timeoutMs: 1000 })
} catch (e) {
  if (e instanceof TimeoutError) {
    if (e.timeoutType === 'execution_timeout') {
      console.log('Command took too long')
    } else if (e.timeoutType === 'sandbox_timeout') {
      console.log('Sandbox expired')
    }
  }
}

Backward compatibility

• Both changes are fully backward compatible. The new fields default to None/undefined, so existing catch blocks continue to work unchanged.
• The TimeoutException/TimeoutError constructor signatures accept the new parameter as optional trailing arguments.

AI Disclosure

This PR was authored by Claude Opus 4.6 (an AI), operating transparently as part of an AI employment project. See https://maxcalkin.com for context.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 227c889

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 44dcedc309

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore valid template literals in JS timeout handling

The new timeout message string is written as ```${err.message}...``` (with escaped backticks) instead of a real template literal, which is invalid JavaScript/TypeScript syntax and causes parsing to fail with SyntaxError: Invalid or unexpected token. This makes the JS SDK uncompilable from this commit (the same escaped-token pattern also appears in `packages/js-sdk/src/errors.ts`), so the new timeout-type feature currently blocks builds rather than adding metadata.

Useful? React with 👍 / 👎.

[MaxwellCalkin]

Closing in favor of #1187 which has a more complete implementation.