perf: show project progress before sandbox preparation - #267
Merged
Conversation
Publish project creation immediately after the database commit. Treat the workspace directory operation as the readiness boundary instead of running a second synthetic Python probe.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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.
Summary
print('ready')call after workspace creation has already started and verified DaytonaDecision
ensureWorkspaceDirectoryremains the real readiness boundary. It is a sandbox operation backed byensureSandbox, so a second synthetic code execution adds a control-plane and toolbox round trip but proves no additional invariant.Verification
pnpm lintpnpm typecheckpnpm turbo build --forcepnpm deadcodepnpm architecture:checkpnpm turbo skills:buildA fresh ordinary-user production app-builder run will measure project-visible latency after merge/deploy.