You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add POST /private/update_delivery_stats that computes delivery latency percentiles (p50, p75, p95, p99) for app, org, and platform scopes
Reuse Observe-style UI via shared DeliveryLatencyPanel (percentile cards + daily trend chart + period selector)
Wire the panel into admin Updates (platform), org dashboard Usage (org), and app Usage (app)
Motivation (AI generated)
Capgo already exposes count-based update success metrics and Native Observe launch/WebView percentiles, but operators still lack a first-class view of how long updates take to download/deliver. Platform, org, and app owners need the same latency distribution language (p50/p75/p95/p99) to spot regressions before success-rate alone moves.
Business Impact (AI generated)
Faster diagnosis of slow OTA delivery improves trust in Capgo cloud updates and helps support/admin catch CDN, bundle size, or regional latency issues earlier. This is a foundation for future alerting and SLA-style delivery reporting.
Visual changes (AI generated)
App Observe now shows update delivery latency percentiles (p50 / p75 / p95 / p99) under the overview cards, synced to the Observe period selector.
Panel detail:
Metric definition (AI generated)
Time to update deliver: device-side time from download start (download_0 / download_zip_start / download_manifest_start) to download complete (download_complete / download_zip_complete)
Prefers metadata.duration_ms when present; otherwise pairs start/complete events within 2 hours (app/org scopes)
Platform scope is admin-only and metadata-only to avoid unbounded pairing across all apps
Test Plan (AI generated)
Unit tests: bunx vitest run tests/update-delivery-stats.unit.test.ts
Admin /admin/dashboard/updates: panel renders for platform admin, empty/demo states behave correctly
Org /dashboard: latency panel appears under usage charts for current org
App /app/:id: latency panel appears for the selected app
Period toggles (1/3/7/30 days) refetch and update cards/chart
Non-admin cannot call platform scope; missing app/org access is denied
Generated with AI
Note
Medium Risk
New authenticated analytics over stats with scope-specific SQL (including lateral pairing for app/org) can be expensive under load; platform scope is gated to admins but org/app queries still scan event data.
Overview
Adds update delivery latency reporting (P50–P99) from device download stats, exposed in the dashboard at org, app, and platform levels.
A new authenticated POST /private/update_delivery_stats endpoint aggregates public.stats download events: for app/org it uses metadata.duration_ms/duration when present, otherwise pairs start/complete actions within two hours; platform scope is admin-only and metadata-only to limit query cost. Responses include overview percentiles, sample/device counts, and daily trend series for 1/3/7/30-day windows, with RBAC on app/org and platform-admin checks.
The UI reuses a shared DeliveryLatencyPanel (percentile cards, trend chart, period selector, loading/error/empty states, demo data) via useUpdateDeliveryStats, wired into org Usage, app Observe (synced period), and admin Updates. i18n strings and unit tests cover response shaping helpers.
Reviewed by Cursor Bugbot for commit 444b0b7. Bugbot is set up for automated code reviews on this repo. Configure here.
Your recent review volume is higher than typical usage, so adaptive limits are currently applied.
Next review available in:26 minutes
Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
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.
No successful run was found on main (caa8138) during the generation of this report, so 6e178ee was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
Show p50/p75/p95/p99 time-to-deliver metrics at platform, org, and app scope using the same Observe-style cards and trend chart.
Co-authored-by: Cursor <cursoragent@cursor.com>
Auto-sync on main dropped the users social username columns from generated types while tests still require them.
Co-authored-by: Cursor <cursoragent@cursor.com>
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: medium. Cursor Bugbot did not complete (skipped due to usage limit), so automated review is unavailable for this run. Human review is needed for the dashboard and API changes; reviewers have been assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
Move the app-scoped delivery latency panel to Native Observe, sync it with the page period, and replace the fake PR preview with a real Observe screenshot.
Co-authored-by: Cursor <cursoragent@cursor.com>
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: medium. Not approving: Cursor Bugbot completed with status skipping and no <!-- BUGBOT_REVIEW --> comment was produced. Human review is still required; reviewers WcaleNieWolny and Dalanir are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: medium. Not approving: Cursor Bugbot did not complete (skipped due to usage limit), and this dashboard/API change exceeds the low-risk approval threshold. Human review is still needed; reviewers are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
Harden duration parsing and query shape, clear stale panel state on scope changes, and cover null/p75 edge cases called out in review.
Co-authored-by: Cursor <cursoragent@cursor.com>
The reason will be displayed to describe this comment to others. Learn more.
Risk: medium. Not approving: Cursor Bugbot completed with status skipping and did not produce a clean automated review. Human review is still required; reviewers WcaleNieWolny and Dalanir are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver
The reason will be displayed to describe this comment to others. Learn more.
Risk: medium. Not approving: Cursor Bugbot completed with status skipping (usage limit) and did not produce a clean <!-- BUGBOT_REVIEW --> result. This dashboard/API change exceeds the low-risk approval threshold; human review is still required. Reviewers WcaleNieWolny and Dalanir are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
The reason will be displayed to describe this comment to others. Learn more.
2 issues found across 7 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="src/composables/useUpdateDeliveryStats.ts">
<violation number="1" location="src/composables/useUpdateDeliveryStats.ts:53">
P3: Missing app/org identifier handling now duplicates the same request invalidation and state reset block. Combining the two predicates would keep this lifecycle behavior in one place and prevent the guards from drifting.</violation>
</file>
<file name="supabase/functions/_backend/private/update_delivery_stats.ts">
<violation number="1" location="supabase/functions/_backend/private/update_delivery_stats.ts:52">
P3: Valid numeric durations longer than 15 characters are excluded, so platform latency silently loses samples such as values with leading zeros or additional fractional precision. Consider safely parsing and checking the numeric value against the 7,200,000 ms bound instead of imposing an unrelated text-length limit.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
The reason will be displayed to describe this comment to others. Learn more.
P3: Missing app/org identifier handling now duplicates the same request invalidation and state reset block. Combining the two predicates would keep this lifecycle behavior in one place and prevent the guards from drifting.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At src/composables/useUpdateDeliveryStats.ts, line 53:
<comment>Missing app/org identifier handling now duplicates the same request invalidation and state reset block. Combining the two predicates would keep this lifecycle behavior in one place and prevent the guards from drifting.</comment>
<file context>
@@ -45,22 +45,37 @@ export function useUpdateDeliveryStats(
async function fetchStats() {
const body = params()
- if (body.scope === 'app' && !body.app_id)
+ if (body.scope === 'app' && !body.app_id) {
+ latestRequest += 1
+ stats.value = null
</file context>
The reason will be displayed to describe this comment to others. Learn more.
P3: Valid numeric durations longer than 15 characters are excluded, so platform latency silently loses samples such as values with leading zeros or additional fractional precision. Consider safely parsing and checking the numeric value against the 7,200,000 ms bound instead of imposing an unrelated text-length limit.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At supabase/functions/_backend/private/update_delivery_stats.ts, line 52:
<comment>Valid numeric durations longer than 15 characters are excluded, so platform latency silently loses samples such as values with leading zeros or additional fractional precision. Consider safely parsing and checking the numeric value against the 7,200,000 ms bound instead of imposing an unrelated text-length limit.</comment>
<file context>
@@ -47,8 +47,14 @@ const startActions = ['download_0', 'download_zip_start', 'download_manifest_sta
- WHEN s.metadata ? 'duration' AND s.metadata ->> 'duration' ~ '^[0-9]+(\.[0-9]+)?$' THEN (s.metadata ->> 'duration')::double precision
+ WHEN s.metadata ? 'duration_ms'
+ AND s.metadata ->> 'duration_ms' ~ '^[0-9]+(\.[0-9]+)?$'
+ AND char_length(s.metadata ->> 'duration_ms') <= 15
+ THEN (s.metadata ->> 'duration_ms')::double precision
+ WHEN s.metadata ? 'duration'
</file context>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
riderx
force-pushed
the
feat/update-delivery-latency-percentiles
branch
from
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary (AI generated)
POST /private/update_delivery_statsthat computes delivery latency percentiles (p50, p75, p95, p99) for app, org, and platform scopesDeliveryLatencyPanel(percentile cards + daily trend chart + period selector)Motivation (AI generated)
Capgo already exposes count-based update success metrics and Native Observe launch/WebView percentiles, but operators still lack a first-class view of how long updates take to download/deliver. Platform, org, and app owners need the same latency distribution language (p50/p75/p95/p99) to spot regressions before success-rate alone moves.
Business Impact (AI generated)
Faster diagnosis of slow OTA delivery improves trust in Capgo cloud updates and helps support/admin catch CDN, bundle size, or regional latency issues earlier. This is a foundation for future alerting and SLA-style delivery reporting.
Visual changes (AI generated)
App Observe now shows update delivery latency percentiles (p50 / p75 / p95 / p99) under the overview cards, synced to the Observe period selector.
Panel detail:
Metric definition (AI generated)
download_0/download_zip_start/download_manifest_start) to download complete (download_complete/download_zip_complete)metadata.duration_mswhen present; otherwise pairs start/complete events within 2 hours (app/org scopes)Test Plan (AI generated)
bunx vitest run tests/update-delivery-stats.unit.test.ts/admin/dashboard/updates: panel renders for platform admin, empty/demo states behave correctly/dashboard: latency panel appears under usage charts for current org/app/:id: latency panel appears for the selected appGenerated with AI
Note
Medium Risk
New authenticated analytics over
statswith scope-specific SQL (including lateral pairing for app/org) can be expensive under load; platform scope is gated to admins but org/app queries still scan event data.Overview
Adds update delivery latency reporting (P50–P99) from device download stats, exposed in the dashboard at org, app, and platform levels.
A new authenticated
POST /private/update_delivery_statsendpoint aggregatespublic.statsdownload events: for app/org it usesmetadata.duration_ms/durationwhen present, otherwise pairs start/complete actions within two hours; platform scope is admin-only and metadata-only to limit query cost. Responses include overview percentiles, sample/device counts, and daily trend series for 1/3/7/30-day windows, with RBAC on app/org and platform-admin checks.The UI reuses a shared
DeliveryLatencyPanel(percentile cards, trend chart, period selector, loading/error/empty states, demo data) viauseUpdateDeliveryStats, wired into org Usage, app Observe (synced period), and admin Updates. i18n strings and unit tests cover response shaping helpers.Reviewed by Cursor Bugbot for commit 444b0b7. Bugbot is set up for automated code reviews on this repo. Configure here.