Skip to content

⚡ Bolt: Optimize debug file filtering in find-files - #23

Draft
piyyy314 wants to merge 2 commits into
mainfrom
bolt/optimize-find-files-debug-filtering-10174549618426875638
Draft

⚡ Bolt: Optimize debug file filtering in find-files#23
piyyy314 wants to merge 2 commits into
mainfrom
bolt/optimize-find-files-debug-filtering-10174549618426875638

Conversation

@piyyy314

Copy link
Copy Markdown
Owner

Bolt Performance Optimization

💡 What

Guarded debug message construction in find() (src/lib/find-files.ts) behind if (debug.enabled) and converted the found array lookup to a Set (foundSet.has(f)).

🎯 Why

Previously, foundAll.filter((f) => !found.includes(f)) ran unconditionally on every file discovery step during project scanning, performing $O(N \cdot M)$ comparisons solely to produce debug logging output.

📊 Impact

  • When debug logging is OFF (default): Entirely skips array allocation and $O(N \cdot M)$ iteration on every directory level scanned.
  • When debug logging is ON: Reduces lookup complexity from $O(M)$ to $O(1)$ per file, making debug filtering $O(N + M)$ instead of $O(N \cdot M)$.

PR created automatically by Jules for task 10174549618426875638 started by @piyyy314

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 21a48f73-a069-487e-88a5-25f0b3b18c6f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

@piyyy314

piyyy314 commented Aug 17, 2026

Copy link
Copy Markdown
Owner Author

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
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