Skip to content

chore: drop the crash dumps that got committed by accident - #2

Merged
proggeramlug merged 1 commit into
mainfrom
chore/drop-crash-dumps
Jul 12, 2026
Merged

chore: drop the crash dumps that got committed by accident#2
proggeramlug merged 1 commit into
mainfrom
chore/drop-crash-dumps

Conversation

@proggeramlug

Copy link
Copy Markdown
Contributor

Nine minidumps (~2.2 MB) from debugging the Windows bring-up were swept into the tree by a git add -A. They are output from the engine's crash filter, not source.

Removed, and tools/.testout/ is gitignored so they cannot come back.

Nine minidumps (~2.2 MB) from debugging the Windows bring-up were swept into the
tree by a `git add -A`. They are build output from the engine's crash filter, not
source. Removed, and gitignored so they cannot come back.
@proggeramlug
proggeramlug merged commit 9df15a5 into main Jul 12, 2026
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@proggeramlug, 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: e3312e16-beeb-4dd5-80f4-b8d6e5e52f36

📥 Commits

Reviewing files that changed from the base of the PR and between 808dca0 and 926ee55.

📒 Files selected for processing (10)
  • .gitignore
  • tools/.testout/dumps/crash_main_21568_6a51d0e7.dmp
  • tools/.testout/dumps/crash_main_24380_6a51cfa4.dmp
  • tools/.testout/dumps/crash_main_25908_6a51cf9f.dmp
  • tools/.testout/dumps/crash_main_27960_6a51d309.dmp
  • tools/.testout/dumps/crash_main_28228_6a51cf98.dmp
  • tools/.testout/dumps/crash_main_28608_6a51d089.dmp
  • tools/.testout/dumps/crash_main_29408_6a51d2cc.dmp
  • tools/.testout/dumps/crash_main_8268_6a51d170.dmp
  • tools/.testout/dumps/crash_main_8880_6a524cba.dmp
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/drop-crash-dumps

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.

@proggeramlug
proggeramlug deleted the chore/drop-crash-dumps branch July 12, 2026 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant