release: 0.54.0 — stop a run, and see what it is costing while it runs - #496
Merged
Conversation
The two gaps the design artifact listed as still open.
- STOP THIS RUN, armed and confirmed like a live start. It signals the
process GROUP (a run is detached into its own group and has children)
with SIGTERM, so the run's own handlers finalize. Stopping the process
is not stopping the sandboxes, and it says so — Reclaim is what ends
those.
- LIVE COST. A run in flight reported its cost as unknown until the
moment it ended, which is the half where knowing changes what you do.
The running usage now travels with the trace into the mid-run flush,
priced by the same estimator as the final figure.
Proven on a real run: `~$0.10 estimated` mid-flight, climbing to `~$0.20`,
then Stop ended it.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
1 participant
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.
release: 0.54.0 — stop a run, and see what it is costing while it runs
The two gaps the design artifact listed as still open.
process GROUP (a run is detached into its own group and has children)
with SIGTERM, so the run's own handlers finalize. Stopping the process
is not stopping the sandboxes, and it says so — Reclaim is what ends
those.
moment it ended, which is the half where knowing changes what you do.
The running usage now travels with the trace into the mid-run flush,
priced by the same estimator as the final figure.
Proven on a real run:
~$0.10 estimatedmid-flight, climbing to~$0.20,then Stop ended it.