⚡ Bolt: Offload blocking I/O to spawn_blocking in get_graph

[EffortlessSteven]

💡 What: Wrapped synchronous, blocking file operations (spec_runtime::load_all_specs_with_context) and CPU-bound work (spec_runtime::build_graph) inside the get_graph HTTP handler with tokio::task::spawn_blocking.

🎯 Why: Running synchronous file I/O and heavy computations directly in async Axum handlers blocks the underlying Tokio worker thread, severely limiting concurrency. This optimization prevents async runtime starvation under high concurrent load.

📊 Impact: Reduces worker thread blockage, massively increasing the potential concurrent throughput of the /platform/graph endpoint without needing to add extra threads.

🔬 Measurement: Verify by executing parallel load tests against the /platform/graph endpoint on a heavily constrained CPU setup and observing no latency spikes or server stallings due to worker pool exhaustion.

---

PR created automatically by Jules for task 2599796225708886830 started by @EffortlessSteven

---

Note

Low Risk
Localized concurrency fix for one read-only endpoint; error mapping is consistent with neighboring handlers and behavior should be unchanged aside from threading.

Overview
The get_graph handler no longer runs spec loading and graph construction on the Tokio worker thread. It clones the platform context and moves load_all_specs_with_context plus build_graph into tokio::task::spawn_blocking, matching the pattern already used for get_openapi and BDD report reads in this module.

Join failures from the blocking task are surfaced as internal errors via PlatformError::internal, with spec-load and graph-build errors unchanged inside the closure.

^{Reviewed by Cursor Bugbot for commit d572fe7. Bugbot is set up for automated code reviews on this repo. Configure here.}

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

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

@EffortlessSteven, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 15 minutes and 31 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 1edd8a5b-4b14-4f83-919a-84ed63434681

📥 Commits

Reviewing files that changed from the base of the PR and between 3debe49 and d572fe7.

📒 Files selected for processing (1)

• crates/gov-http/src/handlers.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-2599796225708886830-e5702ad9

---

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.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_9e4149e5-ba9c-4e6d-a4bd-56f06f6d4cac)

[github-actions]

Test Results

283 tests   245 ✅  11m 36s ⏱️
 25 suites   38 💤
  1 files      0 ❌

Results for commit d572fe7.