e2b@2.62.2
E2B 2.62.2 resolves HTTP/2 stream reset errors during concurrent file uploads and optimizes memory usage during template build hashing.
Why this signal matters
E2B patch release 2.62.2 introduces two main changes: 1) Resolves 'TypeError: fetch failed / NGHTTP2 ENHANCE YOUR CALM' errors during concurrent files.write() calls. In previous versions, Node's HTTP/2 client queued request bodies against a shared 10 MB per-session memory budget, causing parallel or large uploads to reset streams. Uploads now run over HTTP/1.1 with an independent connection pool (configurable via E2B ENVD UPLOAD CONNECTIONS , defaulting to 50), and depleted HTTP/2 sessions are retired and replaced. Failed writes are not retried automatically because writes may have already been applied. 2) Template builds now hash copy() files in 1 MB chunks rather than reading entire files into memory, reducing peak memory while maintaining cache validity as hash outputs remain unchanged.
Actionable summary
E2B released version 2.62.2, addressing concurrent files.write() failures caused by Node HTTP/2 memory budget exhaustion by moving uploads to a dedicated HTTP/1.1 connection pool and replacing OOM-reported sessions. Template build file hashing now streams in 1 MB chunks to lower peak memory.
- Agent usefulness
- 72/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Upgrade to e2b version 2.62.2 if experiencing fetch failures or NGHTTP2 ENHANCE YOUR CALM errors during concurrent file writes.
- Optionally tune the E2B ENVD UPLOAD CONNECTIONS environment variable if upload concurrency limits need adjustment from the default of 50.