Skip to content

fix(serverless): show build status while deploy --wait polls - #135

Merged
Ryank90 merged 2 commits into
feat/serverless-deploy-endpointsfrom
feat/serverless-deploy-build-status
Sep 23, 2026
Merged

Ryank90 merged 2 commits into
feat/serverless-deploy-endpointsfrom
feat/serverless-deploy-build-status

Conversation

@Ryank90

@Ryank90 Ryank90 commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • deploy --wait reports the application status and the newest build status while the image build is still running.
  • The line is printed again only when that status changes. A build list that cannot be read does not fail the wait.

Test plan

  • runware serverless deploy ./app.py --id my-app --gpu-type h100 --wait prints Waiting for application my-app (initializing, build building)... while the build runs
  • The line changes when the build status changes, and the command still exits when the app is active or failed

@coderabbitai

coderabbitai Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. To trigger a review, include coderabbit-review in the PR description. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: b4528603-14c2-4fa3-8470-d93134eff5b8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Ryank90
Ryank90 force-pushed the feat/serverless-deploy-build-status branch from ce4aa32 to 2d25f3d Compare September 22, 2026 16:37
@Ryank90
Ryank90 changed the base branch from rc/serverless to feat/serverless-deploy-endpoints September 22, 2026 16:37
// waitForAppDeploy polls until the app reaches a terminal status. Each
// non-terminal read reports the app status and the newest build status so a
// long image build is not a silent wait.
func waitForAppDeploy(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (non-blocking): waitForAppDeploy copies the poll loop of serverlessapi.Client.WaitApp, and WaitApp now has no caller outside its tests. Add a per-poll callback to WaitApp and keep only the build lookup here; this also removes the second hard-coded 2 * time.Second next to defaultAppPollInterval.

}
}

func TestWaitForAppDeploy_ReportsBuildStatus(t *testing.T) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (non-blocking): The PR says "A build list that cannot be read does not fail the wait", but no test covers it. Add a case where /builds returns 500 and the wait still returns the active app with the no-build message.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed: TestWaitForAppDeploy_ContinuesWhenBuildsFail covers a 500 from /builds; the wait still returns the active app with the no-build message.

A first deploy sat on one waiting line for the whole image build. The wait now says whether that build is queued or building.
A 500 from /builds must not fail the poll; the status line just omits the build.
@Ryank90
Ryank90 force-pushed the feat/serverless-deploy-build-status branch from 2d25f3d to 1a65fb7 Compare September 22, 2026 18:59
@Ryank90
Ryank90 merged commit 6cab6df into feat/serverless-deploy-endpoints Sep 23, 2026
4 checks passed
@Ryank90
Ryank90 deleted the feat/serverless-deploy-build-status branch September 23, 2026 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants