Skip to content

⚡ Optimize dicom_integrate with spawn_blocking#274

Draft
google-labs-jules[bot] wants to merge 1 commit intomainfrom
perf/dicom-integrate-async-8214569025763356980
Draft

⚡ Optimize dicom_integrate with spawn_blocking#274
google-labs-jules[bot] wants to merge 1 commit intomainfrom
perf/dicom-integrate-async-8214569025763356980

Conversation

@google-labs-jules
Copy link
Contributor

@google-labs-jules google-labs-jules bot commented Jan 26, 2026

Offloaded blocking DICOM I/O operations to spawn_blocking to prevent blocking the async runtime. Fixed ClinicalAppState::new to correctly disable PINN when engine is missing.


PR created automatically by Jules for task 8214569025763356980 started by @ryancinsight

High-level PR Summary

This PR optimizes the dicom_integrate endpoint by offloading blocking DICOM I/O operations to spawn_blocking to prevent blocking the async runtime. Additionally, it fixes ClinicalAppState::new to correctly disable the PINN feature when no engine is available by setting enable_realtime_pinn to false in the default configuration. A new test case test_dicom_integrate_endpoint is added to verify the endpoint behavior with the spawn_blocking changes.

⏱️ Estimated Review Time: 15-30 minutes

💡 Review Order Suggestion
Order File Path
1 src/infra/api/clinical_handlers.rs

Need help? Join our Discord

- Wrapped blocking `dicom_service.read_instance` call in `tokio::task::spawn_blocking`
- Used `Arc::clone` and `blocking_read` to safely access `DICOMService` in the blocking task
- Fixed `ClinicalAppState::new` to disable realtime PINN when engine is not provided to prevent runtime panics
- Added `test_dicom_integrate_endpoint` to verify the endpoint behavior
@google-labs-jules
Copy link
Contributor Author

👋 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
Copy link

coderabbitai bot commented Jan 26, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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


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

Copy link

@recurseml recurseml bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review by RecurseML

🔍 Review performed on 0817c38..2b61367

✨ No bugs found, your code is sparkling clean

✅ Files analyzed, no issues (1)

src/infra/api/clinical_handlers.rs

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.

0 participants