Requests session pooling

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Introduce Requests session pooling for GitHub and OpenAI HTTP calls to reduce overhead and improve reliability ⚡️

📊 Key Changes

• Add a persistent requests.Session() to GitHubUtils and route all HTTP methods through self.session.
• Create a module-level _session = requests.Session() in openai_utils.py for OpenAI requests.
• Update OpenAI POST to use the shared session and a tuple timeout (connect=30s, read=600s) for better control.

🎯 Purpose & Impact

• Reduced connection overhead via TCP connection reuse, improving latency in CI workflows.
• More reliable long-running requests to OpenAI with explicit connect/read timeouts.
• Foundation for future enhancements like retry policies and adapter tuning within a single, pooled session.

[UltralyticsAssistant]

👋 Hello @username, thank you for submitting an ultralytics/actions 🚀 PR! This automated message notes your focus on Requests session pooling to improve performance and reliability in our workflows. An engineer will review shortly and assist as needed.

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/actions main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Looks good—thanks for introducing shared sessions to improve connection reuse for both GitHub and OpenAI calls.

[codecov]

Codecov Report

❌ Patch coverage is 77.77778% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
actions/utils/github_utils.py	75.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

Superseded by new review

[UltralyticsAssistant]

🔍 PR Review 2

_{Made with ❤️ by Ultralytics Actions}

The session pooling looks good overall. Please add a way to close the new GitHub session to avoid leaking sockets in long-lived runs.

💬 Posted 1 inline comment

[UltralyticsAssistant]

🔍 PR Review 3

_{Made with ❤️ by Ultralytics Actions}

Nice step toward connection reuse. Please revisit the shared OpenAI session; using a single module-level requests.Session() can introduce thread-safety issues under concurrent load.

💬 Posted 1 inline comment

[UltralyticsAssistant]

🔍 PR Review 4

_{Made with ❤️ by Ultralytics Actions}

Please harden the new session cleanup to avoid destructor-time exceptions; otherwise the session reuse looks good.

💬 Posted 1 inline comment

[UltralyticsAssistant]

🔍 PR Review 5

_{Made with ❤️ by Ultralytics Actions}

Session pooling is a nice win. Please add an explicit way to close the GitHub session instead of depending on __del__, which is unreliable during interpreter shutdown.

💬 Posted 1 inline comment

[UltralyticsAssistant]

💡 MEDIUM: Relying on __del__ for resource cleanup is fragile because destructors may not run (or module globals may already be None) during interpreter shutdown. Please expose an explicit close()/context-manager path and call it from the action lifecycle instead of counting on garbage collection.