enhance the code tool for better stability when loading Docker image

[alcholiclg]

Change Summary

1. enhance the code tool for better stability when loading Docker image (especially for macos).
2. fix bug when loading config.

Related issue number

Checklist

• The pull request title is a good summary of the changes - it will be used in the changelog
• Unit tests for the changes exist
• Run pre-commit install and pre-commit run --all-files before git commit, and passed lint check.
• Documentation reflects the changes where applicable

[gemini-code-assist]

Summary of Changes

Hello @alcholiclg, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the stability and reliability of the code tool, particularly when dealing with Docker images for local sandbox environments. It introduces robust pre-checks for Docker image availability and refines the configuration loading mechanism to ensure that sandbox settings are correctly parsed, thereby preventing potential failures during tool initialization and operation.

Highlights

• Docker Image Pre-check: Introduced a new static method "ensure_local_image_exists" within "SandboxManagerFactory" to proactively verify the presence of a specified Docker image in the local registry. This also helps refresh Docker's image index, enhancing stability during image loading, particularly on macOS.
• Configuration Loading Enhancement: Refactored the configuration parsing logic in "create_manager" to correctly extract sandbox settings from "DictConfig" objects, specifically looking under "config.tools.code_executor". This resolves a bug that could lead to incorrect configuration loading.
• Local Sandbox Image Validation: Integrated the "ensure_local_image_exists" check into the "LocalSandboxManager" creation process. If a Docker image is specified for the local sandbox, the system now validates its local presence, preventing runtime errors if the image is missing.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request enhances the code tool by adding a pre-check for Docker image existence to improve stability, especially on macOS. It also includes a fix for loading the sandbox configuration.

My review focuses on improving the robustness of these changes. I've suggested more specific exception handling in the new Docker image check and a fix for a potential regression in the configuration parsing logic that could affect backward compatibility. I've also recommended preserving original exception tracebacks for better debugging.