Skip to content

fix(ch32v): repair framework validation format string - #1131

Merged
zackees merged 3 commits into
mainfrom
fix/1117-ch32v-format-error
Jul 22, 2026
Merged

fix(ch32v): repair framework validation format string#1131
zackees merged 3 commits into
mainfrom
fix/1117-ch32v-format-error

Conversation

@zackees

@zackees zackees commented Jul 22, 2026

Copy link
Copy Markdown
Member

Closes #1117\n\nJoin the split string literal in �alidate_ch32v_framework so the workspace compiles again.\n\nValidation: soldr cargo test -p fbuild-build-mcu ch32v::orchestrator --lib (7 passed); soldr rustfmt --check crates/fbuild-build-mcu/src/ch32v/orchestrator.rs.

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 17 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: b3e6a783-84a2-418a-b453-566717582051

📥 Commits

Reviewing files that changed from the base of the PR and between 69b51cf and 67df2e0.

📒 Files selected for processing (2)
  • crates/fbuild-build-mcu/src/ch32v/orchestrator.rs
  • crates/fbuild-daemon/src/handlers/operations/deploy.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/1117-ch32v-format-error

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.

@zackees
zackees merged commit 204c7a6 into main Jul 22, 2026
88 of 92 checks passed
@fastled-project-sync fastled-project-sync Bot moved this to Triage in FastLED Tracker Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

fix(ch32v): main fails to compile - adjacent string literals in validate_ch32v_framework format! (#1114 regression)

1 participant