Skip to content

Track total process count#1985

Open
Tomeshwari-02 wants to merge 1 commit into
Karanjot786:mainfrom
Tomeshwari-02:fix-processes-total-count
Open

Track total process count#1985
Tomeshwari-02 wants to merge 1 commit into
Karanjot786:mainfrom
Tomeshwari-02:fix-processes-total-count

Conversation

@Tomeshwari-02

Copy link
Copy Markdown

Summary

  • Cache the process list and total process count separately
  • Keep the public list capped at 50 entries while count reports all process rows
  • Add regression coverage for process output larger than the list cap

Fixes #1975

Testing

  • Not run: Bun is not installed in this environment

@github-actions github-actions Bot added the needs-star PR author has not starred the repo. label Jul 3, 2026
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

Hi @Tomeshwari-02 👋

Star this repo before your PR merges.

Why? GSSoC 2026 contributors who star get priority review and points credit. After you star, push any commit (or re-run this check). The needs-star label lifts automatically.

Thanks for your contribution to TermUI.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Tomeshwari-02, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 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.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f1ed607f-15b5-4ad9-aa73-fd065cd64f17

📥 Commits

Reviewing files that changed from the base of the PR and between 5f479e6 and 77709c5.

📒 Files selected for processing (2)
  • packages/data/src/processes.test.ts
  • packages/data/src/processes.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added area:data @termuijs/data type:testing +10 pts. Tests. labels Jul 3, 2026
@Tomeshwari-02 Tomeshwari-02 marked this pull request as ready for review July 3, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:data @termuijs/data needs-star PR author has not starred the repo. type:testing +10 pts. Tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug] processes.count reports cached top-50 length instead of total process count

1 participant