⚡ Bolt: [performance improvement] Parallelize PR open status checking

[xbmc4lyfe]

💡 What: Use concurrent.futures.ThreadPoolExecutor to execute the gh pr view targeted checks (_pr_is_still_open) concurrently instead of in a sequential loop.

🎯 Why: The original sequential implementation suffered from the N+1 problem. Each PR check invokes the GitHub CLI in a subprocess, waiting for a network request to complete. When the supervisor needs to process dozens of PRs, checking them sequentially introduces significant latency and delays fan-out execution.

📊 Impact: Execution time for _filter_to_still_open_prs drops from O(N) network requests to approximately O(N / 10), substantially accelerating the supervisor restart cycle and reducing the time before worker processes are spun up.

🔬 Measurement: Review supervisor logs before and after the change; the time elapsed between discovering PRs via gh pr list and spawning fan-out workers will be measurably shorter. This can also be observed locally by instrumenting _filter_to_still_open_prs with time.monotonic().

---

PR created automatically by Jules for task 904542757028486197 started by @xbmc4lyfe

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f6b025c8-b224-4106-9ffe-abffa32cd45a

📥 Commits

Reviewing files that changed from the base of the PR and between 7b35ed2 and 56e24a3.

📒 Files selected for processing (2)

• .jules/bolt.md
• ralph_loop/cli.py

📜 Recent review details

🔇 Additional comments (3)

.jules/bolt.md (1)

1-3: LGTM!

ralph_loop/cli.py (2)

13-13: LGTM!

---

547-566: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Refactor

  • Optimized PR state checking to improve filtering performance through parallel execution.

• Chores

  • Updated internal documentation to reflect optimization changes.

Walkthrough

The PR optimizes PR state filtering by replacing sequential gh CLI calls with concurrent execution. A new import enables thread-based parallelism in the filtering function, which now uses ThreadPoolExecutor to check multiple PR states in parallel while preserving exception handling behavior.

Changes

Parallel PR State Checking

Layer / File(s)	Summary
Parallel PR filtering with ThreadPoolExecutor .jules/bolt.md, ralph_loop/cli.py	Documentation explains the N+1 bottleneck in sequential PR state checks. The concurrent.futures module is imported. _filter_to_still_open_prs is refactored to check PR open state in parallel using ThreadPoolExecutor, with per-PR exception capture replacing the sequential loop; CommandError exceptions still cause PRs to be retained in the fan-out set.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit racing through the PR queue,
Found each check was taking too long to pursue,
With threads now fanned out in parallel flight,
The checks zip along, no bottleneck in sight! 🐰⚡

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: parallelizing PR open status checking to improve performance, which directly aligns with the core modification in the codebase.
Description check	✅ Passed	The description is directly related to the changeset, explaining what was changed (ThreadPoolExecutor for concurrent PR checks), why it was needed (N+1 latency problem), and the expected impact on performance.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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/parallel-pr-filter-904542757028486197

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch bolt/parallel-pr-filter-904542757028486197

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 56e24a3069

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove generated Jules note

The root AGENTS.md Docs/Security/Git rules say not to commit generated local artifacts or assistant-generated boilerplate, but this patch adds a Jules-generated metadata note that is unrelated to Ralph behavior. Keeping this file pollutes the repository with tool output rather than the requested performance change, so it should be removed from the commit.

Useful? React with 👍 / 👎.