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 11 minutes and 24 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: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
959b58e to
70814bb
Compare
There was a problem hiding this comment.
Code Review
This pull request renames the canContinue property to willConsumePendingMessages across the agent execution and chat service logic to more accurately describe its function. It also introduces a mechanism to handle final character replies emitted by tools, adding a replyEmitted flag to the done event and updating the UI to reflect when a reply has been sent by a tool. Furthermore, the Docker configuration guide for the extension agent has been updated with recommendations for setting home and working directories, and the parameter descriptions for the group mute tool have been refined for better clarity. I have no feedback to provide as there were no review comments to evaluate.
Summary
canContinue明确为willConsumePendingMessages,让 pending message 消费决策更直观character_reply最终完成分支补充 reply-emitted 标记与 pending drain,避免回复已由工具发送时 trace 仍表现为空输出Verification
yarn fast-build core