fix pre-commit issue

Author: Wendong-Fan

.container/.env.example

@@ -15,4 +15,4 @@ GOOGLE_API_KEY=123456789
 SEARCH_ENGINE_ID=123456789
 
 # For OpenWeatherMap API
-OPENWEATHERMAP_API_KEY=123456789
+OPENWEATHERMAP_API_KEY=123456789

.container/README.md

@@ -11,10 +11,10 @@ develop on it, with Docker.
 
 ## Configure Environment
 Before starting the container, you need to navigate into the
-[.container](../.container) folder and create a `.env` file **with your own 
-API 
-keys**, so that these keys will be present in the environment variables of 
-the container, which will later be used by CAMEL. The list of API keys that 
+[.container](../.container) folder and create a `.env` file **with your own
+API
+keys**, so that these keys will be present in the environment variables of
+the container, which will later be used by CAMEL. The list of API keys that
 can be found in the `.env.example` file.
 
 ```bash
@@ -25,15 +25,15 @@ cp .env.example .env
 ```
 
 ## Start Container
-After configuring the API keys, simply run the following command to start 
+After configuring the API keys, simply run the following command to start
 up the working container. This will automatically set up the environment and
 dependencies for CAMEL. It may take some time, please be patient.
 
 ```bash
 docker compose up -d
 ```
 
-After the build is completed, you can see the image `camel:localdev` in the 
+After the build is completed, you can see the image `camel:localdev` in the
 list of images, along with a started container, `camel-localdev`.
 
 ```bash
@@ -54,7 +54,7 @@ docker compose exec camel bash
 Then you will be in the container environment under the CAMEL directory, with
 all the dependencies installed.
 
-Then You can try running the 
+Then You can try running the
 [role_playing.py](../examples/ai_society/role_playing.py)
 example.
 
@@ -66,43 +66,43 @@ If you see the agents interacting with each other, this means you are all set.
 Have fun with CAMEL in Docker!
 
 ## Save Your Progress
-We support volume mounting in the started container, which means that all 
-of your changes in the CAMEL directory inside the container will be synced 
+We support volume mounting in the started container, which means that all
+of your changes in the CAMEL directory inside the container will be synced
 into the CAMEL repo on your host system. Therefore, you don't need to worry
 about losing your progress when you exit the container.
 
 ## Exit, Stop and Delete the Container
 You can simply press `Ctrl + D` or use the `exit` command to exit the
 container.
 
-After exiting the container, under normal cases the container will still be 
-running in the background. If you don't need the container anymore, you can 
+After exiting the container, under normal cases the container will still be
+running in the background. If you don't need the container anymore, you can
 stop and delete the container with the following command.
 
 ```bash
 docker compose down
 ```
 
 ## Online Images
-For users who only want to have a quick tryout on CAMEL, we also provide the 
+For users who only want to have a quick tryout on CAMEL, we also provide the
 pre-built images on
 [our GitHub Container Registry](https://github.com/camel-ai/camel/pkgs/container/camel).
-Considering the size of the image, we only offer the image with the basic 
+Considering the size of the image, we only offer the image with the basic
 dependencies.
 
-Note that there are some key differences between the local development 
+Note that there are some key differences between the local development
 image and the pre-built image that you should be aware of.
-1. The pre-built image is built upon the source code of each release of CAMEL. 
-   This means that they are not suitable for development, as they don't 
-   contain the git support. If you want to develop on CAMEL, please build 
+1. The pre-built image is built upon the source code of each release of CAMEL.
+   This means that they are not suitable for development, as they don't
+   contain the git support. If you want to develop on CAMEL, please build
    the image by yourself according to the instructions above.
-2. The pre-built image only contains the basic dependencies for running the 
-   examples. If you want to run the examples that require additional 
-   dependencies, you need to install them according to the 
+2. The pre-built image only contains the basic dependencies for running the
+   examples. If you want to run the examples that require additional
+   dependencies, you need to install them according to the
    installation guide in CAMEL's [README](../README.md).
-3. The pre-built image doesn't contain the API keys. You need to set up the 
+3. The pre-built image doesn't contain the API keys. You need to set up the
    API keys by yourself in the container environment.
-4. The pre-built image does not support volume mounting. This means that all 
+4. The pre-built image does not support volume mounting. This means that all
    of your changes in the container will be lost when you delete the container.
 
 To quickly start a container with the pre-built image, you can use the
@@ -123,4 +123,4 @@ command.
 
 ```bash
 python examples/ai_society/role_playing.py
-```
+```

.container/docker-compose.yaml

@@ -11,5 +11,3 @@ services:
       - .env
     user: "${UID:-1000}:${GID:-1000}"
     command: ["tail", "-f", "/dev/null"]
-
-

.env.example

@@ -140,4 +140,4 @@
 
 # Grok API key
 # XAI_API_KEY="Fill your Grok API Key here"
-# XAI_API_BASE_URL="Fill your Grok API Base URL here"
+# XAI_API_BASE_URL="Fill your Grok API Base URL here"

.github/workflows/test_minimal_dependency.yml

@@ -43,4 +43,4 @@ jobs:
         run: |
           source .venv/bin/activate
           pip install pytest dotenv
-          pytest test/integration_test/test_minimal_dependency.py
+          pytest test/integration_test/test_minimal_dependency.py

.pre-commit-config.yaml

@@ -23,7 +23,7 @@ repos:
     hooks:
     - id: check-license
       name: Check License
-      entry: python licenses/update_license.py . licenses/license_template.txt 
+      entry: python licenses/update_license.py . licenses/license_template.txt
       language: system
       types: [python]
       exclude: ^(docs/cookbooks/|examples/usecases/)  # Ignore files under docs/cookbooks and examples/usecases

CONTRIBUTING.md

@@ -4,7 +4,7 @@ Thank you for your interest in contributing to the CAMEL project! 🎉 We're exc
 
 ## Join Our Community 🌍
 
-### Schedule an Introduction Call 📞 
+### Schedule an Introduction Call 📞
 - English speakers: [here](https://cal.com/wendong-fan-5yu7x5/30min)
 - Chinese speakers: [here](https://cal.com/wendong-fan-5yu7x5/30min)
 
@@ -21,7 +21,7 @@ Thank you for your interest in contributing to the CAMEL project! 🎉 We're exc
 
 ### Contributing to the Code 👨‍💻👩‍💻
 
-If you're eager to contribute to this project, that's fantastic! We're thrilled to have your support. 
+If you're eager to contribute to this project, that's fantastic! We're thrilled to have your support.
 
 - If you are a contributor from the community:
   - Follow the [Fork-and-Pull-Request](https://docs.github.com/en/get-started/quickstart/contributing-to-projects) workflow when opening your pull requests.
@@ -40,9 +40,9 @@ Ensuring excellent documentation and thorough testing is absolutely crucial. Her
   - Update any affected example console scripts in the `examples` directory, Gradio demos in the `apps` directory, and documentation in the `docs` directory.
   - Update unit tests when relevant.
 - If you add a feature:
-  - Include unit tests in the `test` directory. 
+  - Include unit tests in the `test` directory.
   - Add a demo script in the `examples` directory.
- 
+
 We're a small team focused on building great things. If you have something in mind that you'd like to add or modify, opening a pull request is the ideal way to catch our attention. 🚀
 
 ### Contributing to the Cookbook Writing 📚
@@ -62,9 +62,9 @@ Here’s how you can contribute to writing cookbooks:
 - Interactive Elements: Whenever applicable, add interactive code cells in Colab that users can directly run and modify.
 
 ##### 1.2. Developing cookbooks for in-progress features
-You can install the latest version of CAMEL from the main branch or a topic branch. This allows you to use the latest codebase, or in-progress features in your cookbook. 
+You can install the latest version of CAMEL from the main branch or a topic branch. This allows you to use the latest codebase, or in-progress features in your cookbook.
 
-`!pip install "git+https://github.com/camel-ai/camel.git@master#egg=camel-ai[all]"` 
+`!pip install "git+https://github.com/camel-ai/camel.git@master#egg=camel-ai[all]"`
 
 Changing the branch and extras section (e.g. remove `#egg=camel-ai[all]`) will behave as expected.
 
@@ -174,10 +174,10 @@ r"""Class for managing conversations of CAMEL Chat Agents.
 Example:
 ```markdown
 Args:
-    system_message (BaseMessage): The system message for initializing 
+    system_message (BaseMessage): The system message for initializing
         the agent's conversation context.
-    model (BaseModelBackend, optional): The model backend to use for 
-        response generation. Defaults to :obj:`OpenAIModel` with 
+    model (BaseModelBackend, optional): The model backend to use for
+        response generation. Defaults to :obj:`OpenAIModel` with
         `GPT_4O_MINI`. (default: :obj:`OpenAIModel` with `GPT_4O_MINI`)
 ```
 
@@ -220,12 +220,12 @@ Avoid using `print` for output. Use Python's `logging` module (`logger`) to ensu
 
 Examples:
 
-- Bad: 
+- Bad:
   ```python
   print("Process started")
   print(f"User input: {user_input}")
   ```
-- Good: 
+- Good:
   ```python
   Args:
   logger.info("Process started")

LICENSE

@@ -198,4 +198,4 @@
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
-   limitations under the License.
+   limitations under the License.

README.ja.md

@@ -632,4 +632,4 @@ CAMELのマルチエージェントフレームワークがインフラ自動化
 [package-download-url]: https://pypi.org/project/camel-ai
 [join-us]:https://eigent-ai.notion.site/eigent-ai-careers
 [join-us-image]:https://img.shields.io/badge/Join%20Us-yellow?style=plastic
-[image-join-us]: https://camel-ai.github.io/camel_asset/graphics/join_us.png
+[image-join-us]: https://camel-ai.github.io/camel_asset/graphics/join_us.png

README.md

@@ -49,7 +49,7 @@
 <br>
 
 
-Join us ([*Discord*](https://discord.camel-ai.org/) or [*WeChat*](https://ghli.org/camel/wechat.png)) in pushing the boundaries of finding the scaling laws of agents. 
+Join us ([*Discord*](https://discord.camel-ai.org/) or [*WeChat*](https://ghli.org/camel/wechat.png)) in pushing the boundaries of finding the scaling laws of agents.
 
 🌟 Star CAMEL on GitHub and be instantly notified of new releases.
 
@@ -382,7 +382,7 @@ We believe that studying these agents on a large scale offers valuable insights
 
 >### Research with US
 >
->We warmly invite you to use CAMEL for your impactful research. 
+>We warmly invite you to use CAMEL for your impactful research.
 >
 > Rigorous research takes time and resources. We are a community-driven research collective with 100+ researchers exploring the frontier research of Multi-agent Systems. Join our ongoing projects or test new ideas with us, [reach out via email](mailto:[email protected]) for more information.
 >
@@ -538,7 +538,7 @@ We are actively involved in community events including:
 - 🎙️ **Community Meetings** — Weekly virtual syncs with the CAMEL team
 - 🏆 **Competitions** — Hackathons, Bounty Tasks and coding challenges hosted by CAMEL
 - 🤝 **Volunteer Activities** — Contributions, documentation drives, and mentorship
-- 🌍 **Ambassador Programs** — Represent CAMEL in your university or local tech groups 
+- 🌍 **Ambassador Programs** — Represent CAMEL in your university or local tech groups
 
 > Want to host or participate in a CAMEL event? Join our [Discord](https://discord.com/invite/CNcNpquyDc) or want to be part of [Ambassador Program](https://www.camel-ai.org/ambassador).