mirror of
https://github.com/stablyai/orca.git
synced 2026-11-16 19:07:41 +00:00
Starting a cloud workspace from a GitHub repository with no clone here showed only a 'Starting <repo> in Orca Cloud…' toast. It now opens the same build sheet as a cloud create from a local clone: Start sandbox, Clone repository with git's progress, Open workspace; the same failure cards and JA-21b billing blocker (plan, hours, spend cap, payment; members get no See plans); Retry; and Back to draft (composer back on Orca Cloud with the GitHub repository picked and the prompt kept). Main: createFromGitHub runs the hosted driver's create path (createSandboxWithProgress, shared with the owned create): boot plan, create, waitForClone, with the same [orca-cloud] progress lines streamed on ephemeralVm:provisionEvent under the window's creation id, the same failure reason lines and codes (hostedCreateFailure), Cancel via ephemeralVm:cancelProvision, and an Idempotency-Key. The workspace id is fixed per creation so a Retry sends the same body. Renderer: the GitHub start is a pending creation with the Orca Cloud recipe and a githubSource; retryBackgroundWorktreeCreation routes it to its own runner. A Retry after a lost answer resends the same key (same sandbox back); after an answered failure it is a new attempt; after a failed open it only opens the sandbox it already has. The paired workspace has no environment-checks step.
5 lines
335 B
TypeScript
5 lines
335 B
TypeScript
// Cancel handles for builds the window shows on a build sheet, by provision (creation) id.
|
|
// `ephemeralVm:cancelProvision` aborts whichever build registered the id: an owned VM or Orca Cloud
|
|
// create, or a GitHub-only Orca Cloud create (GH-CREATE-SHEET).
|
|
export const activeProvisionControllers = new Map<string, AbortController>()
|