fix(cli): surface deployment run failures#289
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
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. |
|
Warning Review limit reached
Next review available in: 40 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
active/lastUsed: -even though the API already returned the exact run failure.lastRunStatus, rawlastError, andintegrationWatchHealththrough the realdeployments list --jsonpath.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:
After, deployment state is disambiguated from run and watch health, and the captured error is visible:
Verification
5a0a49658f31f6367d268730bf16951da17ee364pnpm --filter @agentworkforce/cli buildnode --test packages/cli/dist/list-command.test.js(10/10)pnpm --filter @agentworkforce/cli typecheckgit diff --checkrunDeploymentList --jsonpath preserves raw CRLF/ANSI error text while human output normalizes and bounds it.