[web] Fix recompute progress layout - #1953
Conversation
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
|
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. |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
Next review available in: 13 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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe web recompute indicator now uses an indeterminate spinner for null progress, with updated accessibility and layout behavior. Storybook and tests cover delayed multi-dataset recomputation. A production incident baseline entry documents a failed ClickHouse consumer deployment. ChangesRecompute indicator
Production incident baseline
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
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 |
|
Storybook previews for This comment updates automatically on each PR push. |
|
@coderabbitai review |
✅ Action performedReview finished.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/production-incident-baseline.md`:
- Around line 16867-16871: Separate the completed mitigation from pending
recovery actions in the incident entry: keep the statement that no production
mutation occurred as the mitigation, and move “Restore the consumers” plus its
verification criteria into a clearly labeled recovery plan or next-steps
section. Link the reviewed deployment recovery path explicitly so the documented
steps are actionable without undocumented operator knowledge.
- Around line 16846-16866: Add primary-source links supporting each incident
claim in the Status, Symptoms, User impact, Evidence, and Root cause bullets,
including monitor output for the five pending operations, data-availability
evidence, and the deployment script or runbook documenting pre-scaling. Link
authoritative Docker Swarm documentation or an incident record for the stated
failure mechanism, and label Root cause as suspected unless directly verified by
evidence.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 2208c012-c497-4470-80f6-ddae23adfa38
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (5)
docs/production-incident-baseline.mdpackages/web/package.jsonpackages/web/src/components/ProcessingStatusWidget.stories.tsxpackages/web/src/components/RecomputeStatusIndicator.test.tsxpackages/web/src/components/RecomputeStatusIndicator.tsx
Asherlc
changed the title
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
…ation-expectations # Conflicts: # docs/production-incident-baseline.md
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
Summary
Replaces the custom indeterminate recomputation SVG with
react-spinnersand keeps the progress row left-aligned with wrapping labels.Adds regression and Storybook coverage for the long multi-dataset status, and records the unresolved quiesced-consumer production incident plus the transient CI setup failure.
Validation
Passed
pnpm lint, root/server/webtsc --noEmit,pnpm test(13,450 tests), the web build, and bundle-size checks.