Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 12 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ 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 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d352a47504
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| id: event.id, | ||
| title: `${event.namespace} • ${event.status}`, | ||
| time: formatDate(event.created_at), | ||
| desc: truncate(text(event.extracted_summary, text(event.raw_text, "No summary available"))), |
There was a problem hiding this comment.
When an event has no extracted_summary, this copies raw_text into timelineEvents.desc; because /pandora passes the entire dashboardData object into a "use client" component, that value is serialized into the browser payload even though the current UI no longer renders the timeline. For events captured through the existing memory event path without a summary, this can expose private or secret-like memory text in page source/devtools, so the loader should only return redacted/summary-safe fields to the client.
Useful? React with 👍 / 👎.
| for (const namespace of NAMESPACES) { | ||
| const [events, packs, profiles, openLoops, captureCandidates, reviewQueue, pruningCandidates] = await Promise.all([ | ||
| readRows<MemoryEventRow>(client, "memory_events", input.userId, namespace, warnings, { limit: 500, orderBy: "created_at" }), | ||
| readRows<ContextPackRow>(client, "memory_context_packs", input.userId, namespace, warnings, { limit: 50, orderBy: "created_at" }), |
There was a problem hiding this comment.
This fetches the 50 newest context packs across all pack types and only later filters for pack_type === "master". In any namespace with more than 50 newer daily/weekly/project packs, the active master pack can be truncated out before buildSpace and buildStats run, causing the live dashboard to report the namespace as degraded or miss duplicate active masters even though the master rows exist.
Useful? React with 👍 / 👎.
|
|
||
| const openLoopCount = namespaces.reduce((sum, ns) => sum + countStatus(ns.openLoops, ["open", "acknowledged"]), 0); | ||
| const needsReview = namespaces.reduce((sum, ns) => sum | ||
| + ns.captureCandidates.filter((row) => row.status === "pending" || row.requires_review === true).length |
There was a problem hiding this comment.
This treats every row with requires_review === true as still needing review, regardless of its lifecycle status. Since capture candidates are created with review required and existing review/capture flows move them to statuses such as approved, rejected, captured, or duplicate without clearing that flag, the dashboard's needsReview count can stay inflated by already-processed candidates and make the work queue look permanently non-drained.
Useful? React with 👍 / 👎.
1 participant
Status: open. CI is failing at typecheck. Do not merge until green. Core loader work is on branch live-data; remaining fix is a small type compatibility patch.