Evaluation: Incomple Langfuse traces sycned#702
Conversation
|
Warning Rate limit exceeded
⌛ 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 (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
Summary
Target issue is #671
Checklist
Before submitting a pull request, please ensure that you mark these task.
fastapi run --reload app/main.pyordocker compose upin the repository root and test.Notes
Earlier, if a score was missing from even one trace, it was simply left out of the summary. So users would only see scores that were present everywhere, which meant some useful information could be hidden. In this case, only the
complete_scorewas visible because it existed across all traces.Now, scores are included even if they show up in just some traces. Instead of dropping them, we calculate their average based only on the traces where they actually exist. So users will now see both
complete_score(which appears in all traces) andpartial_score(which might appear in only one or a few traces).In simple terms, nothing gets silently ignored anymore. Even partial data is surfaced, giving users a clearer and more complete picture of what’s going on.