Skip to content

fix(api): remove duplicate AnalyzeOptions import in m4 baseline - #701

Closed
DecisionNerd wants to merge 2 commits into
mainfrom
fix/main-baseline-dup-import
Closed

DecisionNerd wants to merge 2 commits into
mainfrom
fix/main-baseline-dup-import

Conversation

@DecisionNerd

@DecisionNerd DecisionNerd commented Aug 12, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • m4_entry_baseline.rs on main imports AnalyzeOptions twice, failing Bazel compile.
  • Remove the duplicate so the ComputePool land train can proceed.

Test plan

  • CI Gate CLEAN

Made with Cursor


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Note

Fix duplicate AnalyzeOptions import and update expected workload count in m4 baseline test

  • Removes a redundant use graphforge_core::AnalyzeOptions import in m4_entry_baseline.rs.
  • Updates the expected workload count in short_ci_matrix_runs_through_public_facade_under_fixed_two_workers from 11 to 12.

Macroscope summarized a8f6dd2.

Unblocks Bazel compile of m4_entry_baseline after a bad import merge.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions github-actions Bot added the core Core source code changes label Aug 12, 2026
@coderabbitai

coderabbitai Bot commented Aug 12, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 5 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ba1da559-4e7f-41f5-844e-df399e4bb31d

📥 Commits

Reviewing files that changed from the base of the PR and between 1acf5b0 and a8f6dd2.

📒 Files selected for processing (1)
  • crates/graphforge-api/tests/m4_entry_baseline.rs

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

@blacksmith-sh

This comment has been minimized.

The id list already listed twelve short_ci workloads; the length
assertion still expected 11 and failed Bazel m4_entry_baseline.

Co-authored-by: Cursor <cursoragent@cursor.com>
@DecisionNerd

Copy link
Copy Markdown
Contributor Author

Superseded: duplicate AnalyzeOptions import was removed on tip via #609 (7ee8ae4). Closing to avoid thrash.

@DecisionNerd
DecisionNerd deleted the fix/main-baseline-dup-import branch August 13, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core Core source code changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant