Version Packages#813
Open
sandy-bonk[bot] wants to merge 1 commit into
Open
Conversation
3dc53bc to
7c2ccb0
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@cloudflare/sandbox@0.12.5
Patch Changes
#786
750ca4dThanks @aron-cf! - Instrument the bridge API with Cloudflare custom spans. Each endpoint now emitsa
bridge.<operation>span annotated with the sandbox ID, container UUID, andoperation-specific metadata (command, file path, port, session ID, and so on),
so requests are traceable end to end. Enable tracing with
observability.traces.enabledin your Worker configuration.#786
750ca4dThanks @aron-cf! - Fill the warm pool in bounded-parallel batches instead of one container at atime, so it primes and recovers far faster after a burst. Tune the batch size
with
WARM_POOL_SCALE_BATCH_SIZE(default 5, clamped to 20).#786
750ca4dThanks @aron-cf! - Refill the warm pool the moment it drains instead of waiting for the nextbackground tick. After a burst consumes warm containers, replenishment now
starts immediately, cutting the latency tail for sandboxes created during
sustained or back-to-back bursts.
#786
750ca4dThanks @aron-cf! - Let the warm pool know its instance ceiling up front via theWARM_POOL_MAX_INSTANCESbridge variable. Set it to match your container'smax_instancesso the pool makes correct capacity decisions without firstcrashing into the limit.
0(the default) preserves the existing auto-learnbehaviour.