🔧 fix: clamp time display to 0-100% to prevent negative ms values#807
🔧 fix: clamp time display to 0-100% to prevent negative ms values#807guangzan wants to merge 1 commit intoelysiajs:mainfrom
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. 📒 Files selected for processing (1)
WalkthroughA bounds-checking modification ensures the left position value in the move function is clamped between 0 and 100, preventing out-of-range positioning. The computed left value now undergoes range validation before assignment. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
719f3c6 to
625d187
Compare
When mouse moves outside the left edge of the OpenTelemetry timeline, the displayed time could show negative values (e.g. -0.03ms). Clamp left percentage to [0, 100] range so time always displays 0ms-25ms.
625d187 to
6201b6b
Compare
When mouse moves outside the left edge of the OpenTelemetry timeline, the displayed time could show negative values (e.g. -0.03ms). Clamp left percentage to [0, 100] range so time always displays 0ms-25ms.
After:
Summary by CodeRabbit