docs: record Hugging Face corpus audit findings#24
Conversation
|
Warning Review limit reached
More reviews will be available in 18 minutes and 24 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus 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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f591b620b1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - [x] Refine conventional-search ranking and snippet behavior now that the first SearchKit backend works end to end. | ||
| - [x] Validate the current refinement pass against a broader checked-in fixture corpus with near-miss ranking and longer-body snippet cases. | ||
| - [ ] Validate whether the current refinement pass is enough for ordinary app callers against larger real app corpora. | ||
| - [x] Validate whether the current refinement pass is enough for ordinary app callers against larger real app corpora. |
There was a problem hiding this comment.
Keep real-app corpus validation open
This newly checked roadmap item claims the refinement pass has been validated against larger real app corpora, but the recorded audit only uses the first 100 rows from three public Hugging Face datasets and the new findings doc explicitly says it does not stand in for a real app's private corpus. When maintainers use the roadmap to decide what Milestone 4 work remains, this marks a validation gap as completed even though the documented evidence says the next signal is still a caller-owned corpus.
Useful? React with 👍 / 👎.
Summary
Verification