e2b-dev / e2b-dev/code-interpreter
Contribute example: execution telemetry or error-handling patterns
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 228
- Avg merge
- 48m
- Merged PRs (30d)
- 5
Description
Hi E2B team! I'd like to contribute an example to help users with common patterns. Before opening a PR, wanted to confirm direction:
Options I can ship:
-
Execution telemetry wrapper — Uses SDK callbacks (onStdout/onStderr) to capture timing, output stats from the Execution object, produces JSON summary. No infra metrics, just SDK best practices.
-
Error-handling patterns — Demonstrates timeouts, retries for transient errors, cleanup patterns, graceful degradation.
-
Real use case — CSV → analysis → chart pipeline showcasing file ops, streaming, and structured output.
Questions:
- Which would be most valuable for the community?
- Should this live in
examples/here or in e2b-cookbook?
Happy to ship whichever helps users most. Let me know!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes three different example directions and asks whether the work belongs in examples/ or e2b-cookbook. First wait for a maintainer to select the scope and location, then review the chosen example area and its existing patterns. Done means the agreed example is added in the selected location and demonstrates the requested SDK behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python, typescript
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100