Filter cycling analytics to cycling activities - #1558
Conversation
|
Warning Review limit reached
Next review available in: 45 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: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
📝 WalkthroughWalkthroughRepositories that query ClickHouse for cycling analytics are refactored to filter by an explicit ChangesCycling-only activity type filtering
Estimated code review effort: 4 (Complex) | ~60 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 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 |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Storybook previews for This comment updates automatically on each PR push. |
There was a problem hiding this comment.
All reported issues were addressed across 13 files
Confidence score: 5/5
- Safe to merge after the addressed issues were fixed.
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Requires human review: Auto-approval blocked by 4 unresolved issues from previous reviews.
Re-trigger cubic
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
0 issues found across 2 files (changes from recent commits).
Requires human review: Auto-approval blocked by 4 unresolved issues from previous reviews.
Re-trigger cubic
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Addressed the actionable items from the Cubic review summary. |
There was a problem hiding this comment.
All reported issues were addressed across 8 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
0 issues found across 1 file (changes from recent commits).
Requires human review: Auto-approval blocked by 2 unresolved issues from previous reviews.
Re-trigger cubic
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
There was a problem hiding this comment.
Asherlc has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
0 issues found across 3 files (changes from recent commits).
Auto-approved: Bug fix filtering cycling analytics to cycling-only activities by replacing ENDURANCE_ACTIVITY_TYPES with CYCLING_ACTIVITY_TYPES across six repositories, with updated SQL joins and test coverage.
Re-trigger cubic
Fixes the cycling training page so server-side analytics only include cycling activity types instead of broad endurance activity types. This updates power, estimated threshold power, fitness/fatigue/form, aerobic efficiency, vertical ascent, variability, pedal dynamics, and the power-curve fallback sample path. The root cause was reuse of ENDURANCE_ACTIVITY_TYPES in repositories backing /training/cycling, which allowed walks/runs/hikes into cycling charts. Validated with focused Vitest coverage, TypeScript, and Biome; full changed lint reached analytics SQL lint but local ClickHouse was unavailable at 127.0.0.1:8123.
Summary by cubic
Filters cycling training analytics to cycling-only activities so runs, walks, and hikes no longer affect cycling charts. Applies to power and power curve, eFTP, PMC (fitness/fatigue/form), aerobic efficiency, vertical ascent, variability, pedal dynamics, ramp rate, and training monotony.
ENDURANCE_ACTIVITY_TYPESwithCYCLING_ACTIVITY_TYPESacross Power, Efficiency, CyclingAdvanced, and PMC repositories, plus raw activity counts; standardized SQL tohas({activityTypes:Array(String)}, ...).analytics.activity_summary(no FINAL) and filters to cycling;ActivitySensorStore.getPowerCurveSamples(days, userId, timezone, activityTypes)added and wired throughclickhouse-activity-sensor-analyticsandlimited-activity-sensor-store.analytics.daily_endurance_loadjoined toanalytics.activity_summary, filtered to cycling; ramp rate window bounded todays + 42for stable CTL deltas; PMC filters activity queries and the fallback max HR baseline to cycling. Tests updated to assert cycling-only behavior, the newactivityTypesparam, and update the dedup integration to recognize the cycling ramp rate query.Written for commit 265e8fd. Summary will update on new commits.
Summary by CodeRabbit
New Features
Bug Fixes
Tests