[Bugfix] Use the correct taskData when retrieving descriptors#422
[Bugfix] Use the correct taskData when retrieving descriptors#422
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 9 minutes and 52 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Fixes descriptor discovery to consistently use the correct TaskData instance when waiting for and reading discovery results, preventing mismatched state when a custom filter is supplied.
Changes:
- Ensures
retrieveDescriptors()always wires the active stacktaskDatainto the filter used by the discovery callback. - Reads completion status from the local
taskDatarather than indirectly throughpFilter->taskData. - Simplifies
getDescriptor()filter construction while relying onretrieveDescriptors()to bindtaskData.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
0bdbd2c to
8493b87
Compare
8493b87 to
abfe6c8
Compare
No description provided.