fix(stats): use rolling host latency for live overlay - #59
Conversation
|
Warning Review limit reached
Next review available in: 15 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
改了啥喵
hostLatency改为实时窗口平均值。为啥要改
之前客户端把整个会话的累计平均主机延迟直接显示在实时浮层里。一次网络或编码抖动留下的高延迟样本会一直拖住后续数值,看起来就像主机延迟持续上升,杂鱼统计把历史包袱背太久了。
验证
npm run test:sunshine-mockgit diff --checkassembleHap未执行成功:本机缺少 DevEco/Hvigor,脚本尝试从 npm 获取不存在的hvigor包。关联 issue:#57