Skip to content

fix(cli): surface deployment run failures#289

Merged
khaliqgant merged 1 commit into
mainfrom
fix/deployments-list-failure-visibility
Jul 17, 2026
Merged

fix(cli): surface deployment run failures#289
khaliqgant merged 1 commit into
mainfrom
fix/deployments-list-failure-visibility

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Jul 17, 2026

Copy link
Copy Markdown
Member

Summary

  • Fix the CLI render gap that made the cloud#2696 observability failure look like active / lastUsed: - even though the API already returned the exact run failure.
  • Preserve lastRunStatus, raw lastError, and integrationWatchHealth through the real deployments list --json path.
  • Separate deployment lifecycle, last-run status, and integration-watch health in the human table, with a bounded control-normalized error section.

This makes two distinct known failures visible instead of collapsing them into the same healthy-looking row:

Before / after

Before, the E2BIG row appeared active with no last use and no failure detail:

name                       status  deployed              lastUsed  agentId
hoopsheet-maintainability  active  2026-07-17 12:55 UTC  -         agent-e2big

After, deployment state is disambiguated from run and watch health, and the captured error is visible:

name                       deployment  lastRun  watch      deployed              lastUsed  agentId
hoopsheet-maintainability  active      failed   unhealthy  2026-07-17 12:55 UTC  -         agent-e2big

Errors:
  hoopsheet-maintainability: /home/daytona/session/cmd.sh: line 3: /usr/bin/timeout: Argument list too long

Verification

  • Independently reviewed head: 5a0a49658f31f6367d268730bf16951da17ee364
  • pnpm --filter @agentworkforce/cli build
  • node --test packages/cli/dist/list-command.test.js (10/10)
  • pnpm --filter @agentworkforce/cli typecheck
  • git diff --check
  • Independent review verified the real runDeploymentList --json path preserves raw CRLF/ANSI error text while human output normalizes and bounds it.

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@cursor

cursor Bot commented Jul 17, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@khaliqgant, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4463823a-a648-4205-83ef-829c0b05ba81

📥 Commits

Reviewing files that changed from the base of the PR and between 33c59c0 and 5a0a496.

📒 Files selected for processing (3)
  • packages/cli/CHANGELOG.md
  • packages/cli/src/list-command.test.ts
  • packages/cli/src/list-command.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/deployments-list-failure-visibility

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.

@khaliqgant
khaliqgant merged commit 17aec50 into main Jul 17, 2026
3 checks passed
@khaliqgant
khaliqgant deleted the fix/deployments-list-failure-visibility branch July 17, 2026 15:16
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.

1 participant