Files
orca/cloud/apps/sandbox-control/migrations/0053_sandbox_setup_failed.sql
T
Neil d441463abb perf(cloud): a create answers at ready; member git identities install after it (CREATE-GIT-ASYNC)
POST /v1/sandboxes kept the response open ~2.3 s after orcad was ready while syncMemberGit ran (and again inside boot when the creator had GitHub connected). A create now records the owner device, answers, and installs member identities in ctx.waitUntil. The VM is told the setup is pending (ORCA_GIT_SETUP=pending -> ~/.orca-sandbox/git-setup.pending); its git shim holds commit/push/merge/... up to 15 s until orca-sandbox-members writes git-setup.ready, and on a failed or stalled setup stops them with what to do instead of committing as the workspace identity. Read-only git and fetches never wait: the boot already routes the workspace credential. A failed install is kept on the row (0053 git_setup_failed_at) and shown as sandbox.gitSetup 'failed' to clients sending feature git-setup; any later boot or successful sync clears it. Wake, resume, restart and grants are unchanged (synchronous).
2026-11-11 19:29:18 -08:00

5 lines
362 B
SQL

-- CREATE-GIT-ASYNC: a create answers once orcad is ready and installs member git identities after.
-- Set when that background setup failed (cleared by the next successful sync); the sandbox view then
-- reports gitSetup 'failed' so the desktop can say why git won't commit or push as the teammate.
ALTER TABLE sandboxes ADD COLUMN git_setup_failed_at INTEGER;