Repository navigation
fix(nova): keep large repository baseline creation within output limits - #364
Conversation
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
No actionable comments were generated in the recent review. WalkthroughThe E2B checkout now runs ChangesE2B Baseline Output
Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Possibly related PRs
Merge Risk:
|
Git's initial commit prints every added path. On Supercli, that exceeds Nova's 20 KB command-output limit, aborting setup during
initializing Git baselineeven though archive extraction succeeds.Use quiet Git initialization and commit for this control-plane baseline operation. Keep command-output limits, error handling, and repository isolation unchanged. Add a 600-file regression that fails with the previous implementation and verifies a clean, complete baseline with bounded output.
Verified the failure with an archive of
yashdev9274/supercliat main, then verified the fix on Default, 1 CPU / 4 GB, and 2 CPU / 8 GB E2B templates. Each completed checkout with zero baseline stdout/stderr, preserved an edit across filesystem-only pause/reboot, and exported the edit as a patch. Tests used a local Git archive of the actual repository, not production GitHub credentials; all disposable sandboxes were deleted.Validation: 47 sandbox tests, web TypeScript check, scoped ESLint, and
git diff --checkpass. After deployment, use a new Nova thread for sessions whose initial setup already failed; existing retained workspaces are not reset.Summary by CodeRabbit