⚡ Bolt: Disable YOLO verbose mode to reduce I/O overhead

[kingkillery]

💡 What: Added verbose=False to Ultralytics YOLO model.predict() calls in FFDNetDetector.extract_widgets().
🎯 Why: Ultralytics YOLO defaults to printing verbose inference details to stdout for every prediction. In loops over many pages, this synchronous I/O blocks execution and creates a performance bottleneck.
📊 Impact: Eliminates blocking stdout writes during inference, leading to measurably faster execution, especially on multi-page PDFs.
🔬 Measurement: Verify by running inference on a multi-page PDF and observing faster, quieter execution without terminal spam. Tests ensure no regressions in detection output.

---

PR created automatically by Jules for task 5786829856752787198 started by @kingkillery

Summary by CodeRabbit

• Performance Improvements

  • Optimized YOLO model inference execution by reducing unnecessary logging output during predictions across both ONNX and PyTorch inference paths.

• Documentation

  • Added learning notes documenting inference optimization techniques and planning documentation for future improvements.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Walkthrough

Performance optimization implemented by adding verbose=False parameter to YOLO model.predict() calls in the inference pipeline to eliminate stdout logging overhead. Change documented with a learning note and PR plan.

Changes

Cohort / File(s)	Summary
Documentation & Learning Notes .jules/bolt.md, plan.md	New Markdown documents added: learning note on YOLO model.predict() synchronous logging behavior and optimization strategy checklist.
Inference Optimization commonforms/inference.py	Updated FFDNetDetector.extract_widgets to pass verbose=False to self.model.predict() calls in both ONNX (fast) and PyTorch branches to suppress verbose output.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hop, hop, verbose be gone!
Silent predictions race on and on.
No logging overhead, just speed—
⚡ That's all a rabbit needs!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: disabling verbose mode in YOLO predict calls to reduce I/O overhead, which is the core functional change across the modified files.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-optimize-yolo-inference-5786829856752787198

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.jules/bolt.md:
- Line 1: The header "## 2024-05-24 - Ultralytics YOLO Synchronous Logging
Overhead" in .jules/bolt.md should be verified and either updated or annotated:
confirm whether "2024-05-24" is the original documentation date or a mistake; if
it’s incorrect, replace it with the PR date "2026-04-08" (or the correct current
date) in the header, or add a parenthetical note like "(originally documented
2024-05-24)" to preserve provenance; update the header text accordingly to "##
2026-04-08 - Ultralytics YOLO Synchronous Logging Overhead" or add the
provenance note so the date accurately reflects the context of this PR.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6d32d9d5-1f6e-4b00-b2f4-0fca41183bb4

📥 Commits

Reviewing files that changed from the base of the PR and between e00f2d1 and 550d887.

📒 Files selected for processing (3)

• .jules/bolt.md
• commonforms/inference.py
• plan.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Verify the date in the learning note.

The learning note is dated "2024-05-24", but this PR was created on "2026-04-08". If this represents when the learning was originally documented elsewhere, that's fine. Otherwise, consider updating to reflect the current optimization work.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.jules/bolt.md at line 1, The header "## 2024-05-24 - Ultralytics YOLO
Synchronous Logging Overhead" in .jules/bolt.md should be verified and either
updated or annotated: confirm whether "2024-05-24" is the original documentation
date or a mistake; if it’s incorrect, replace it with the PR date "2026-04-08"
(or the correct current date) in the header, or add a parenthetical note like
"(originally documented 2024-05-24)" to preserve provenance; update the header
text accordingly to "## 2026-04-08 - Ultralytics YOLO Synchronous Logging
Overhead" or add the provenance note so the date accurately reflects the context
of this PR.