Pre release 0.4.0

[pan-x-c]

Description

As the title says

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @pan-x-c, 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 primarily focuses on preparing the project for its 0.4.0 release by incrementing version numbers across the codebase. It also includes crucial adjustments to the dependency management system, particularly within the Docker build process, to enhance stability and address potential installation issues for key machine learning libraries. Additionally, a test file has been refactored to ensure more robust and isolated testing practices.

Highlights

• Version Update: The project version has been updated to 0.4.0 in both pyproject.toml and trinity/__init__.py, signaling a new release.
• Dependency Installation Improvements: Updates were made to the Dockerfile and pyproject.toml to refine the installation of Megatron-related dependencies, specifically transformer_engine and flash_attn, by adding troubleshooting comments and adjusting installation flags like --no-build-isolation.
• Test Suite Refinement: The swanlab_test.py file was improved to properly handle environment variables during testing by saving and restoring the original SWANLAB_API_KEY, and the unittest.main() block was removed for better integration with test runners.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (4)
  • .github/workflows/docker.yaml
  • .github/workflows/docker/docker-compose.yaml
  • .github/workflows/pre-commit.yaml
  • .github/workflows/unittest.yaml

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 prepares for the 0.4.0 release by updating the version number and dependencies. The changes in the Dockerfile to explicitly install megatron dependencies are noted. I've suggested an improvement to maintain these dependencies from a single source of truth in pyproject.toml. Other changes, including test improvements and a bug fix in an f-string, look good.

[pan-x-c]

/unittest-all

[pan-x-c]

/unittest-all

[pan-x-c]

/unittest-all

[pan-x-c]

/unittest-all