Merge upstream: Return replay retry state from orchestration recovery (#1728)#47
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 32 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro 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 |
What
Cherry-picks upstream commit
6de4b47e(PR #1728) onto the fork.Upstream changes
Enhances orchestration recovery to return replay retry state, allowing the UI to surface retry information when event replay fails. Adds comprehensive tests for the retry state machine.
orchestrationRecovery.ts: NewReplayRetryStatetype, retry tracking with exponential backoff,shouldRetryReplayhelper.orchestrationRecovery.test.ts: 10 new test cases covering retry state transitions.__root.tsx: Integrates retry state into the recovery effect, surfaces retry UI.Conflict resolution
None -- clean cherry-pick with no conflicts. Auto-merged
orchestrationRecovery.tsand__root.tsx(fork changes are in different sections).Verification
bun typecheckpasses (all 7 packages)orchestrationRecovery.test.tspasses (12 tests)!threadguard in__root.tsxpreserved