Repository navigation
Conversation
levb
force-pushed
the
lev-storage-rationalize
branch
from
May 26, 2026 19:45
a8fab3c to
7f8bf0d
Compare
adds route to create and invalidate API keys via internal services --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ixes e2b-dev#1280) (e2b-dev#2488) ### 📝 Description This PR addresses **Issue e2b-dev#1280** and recent discussions in the E2B Discord community regarding build failures with non-Debian base images. Currently, the provisioning scripts rely on `apt` and Debian-specific filesystem layouts. Users attempting to use images like Alpine or CentOS often face cryptic build errors. This documentation update explicitly states the requirement for Debian/Ubuntu-based images to prevent this confusion. ### 🛠️ Changes - Added a **Limitations** section to the documentation. - Explicitly noted that custom template builds require Debian/Ubuntu-based images with `apt`. - Clarified that non-Debian images (Alpine, CentOS/RHEL, etc.) are currently unsupported. ### 🔗 Context - **Related Issue:** e2b-dev#1280 - **Community Discussion:** [Discord Thread](https://discord.com/channels/1092455714431180995/1496072388335370314) ### 💡 Motivation To save users time debugging build failures caused by incompatible package managers (e.g., `apk`, `yum`) and to set clear expectations for custom template creation. --------- Co-authored-by: AdaAibaby <shaolila@buaa.edu.cn>
## Summary Moves blocked-team enforcement from opt-in handler checks into shared middleware for API and dashboard API routes, with explicit allowlists for recovery/read/delete paths. ## Changes - Added blocked-team middleware for `packages/api` and `packages/dashboard-api` - Added route allowlists for blocked teams - Add late team-resolution checks for access-token/user-auth API paths --------- Co-authored-by: Jakub Novak <jakub@e2b.dev> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…dev#2829) Add tracing attributes to all GRPC methods in orchestartor
Replace the OpenRangeReader return type io.ReadCloser with a context-aware RangeReader and collapse scattered reader wrappers (offset/section/capture/ observable/decompress) into a single io_wrappers.go. Drops the cacheWriteThroughReader in favor of a reusable captureReader with optional drain-on-close for codecs that stop short of EOF on their source.
levb
force-pushed
the
lev-storage-rationalize
branch
from
May 27, 2026 19:30
7f8bf0d to
58a13a6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unify the storage read path on one RangeReader interface (io.Reader + Close(ctx)) so no wrapper stores a context. Cross-cutting read concerns — OTEL timer/span/gauge, cancellation, and decompression — collapse into a single
readerconfigured by with* builder methods; backend leaves are adapted via NewRangeReader.