Order doctor's diagnostic references deterministically - #870
Conversation
Several diagnostics can share a name, so sorting on provider and name alone left the order to settle on set iteration order. Two identical `ref doctor` runs then produced different reports. Adds the slug as the tiebreak, and drops a docstring reference to a `--only` flag that does not exist.
|
Warning Review limit reached
Next review available in: 28 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 (4)
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 |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Follow-up to #865.
ref doctorproduced a different report on each run. Several diagnostics share a name (the four ozone ones are all "Ozone Diagnostics"), andDiagnosticReference.sort_keywas provider plus name only, so the tie broke on set iteration order. Two identical runs gave differentmissing-reference-datadetails, which makes a pasted report hard to diff.--onlyflag that does not exist.Found by running the checks against a real deployment and diffing
--format jsonacross three runs. Same three runs are now byte-identical.