chore: bump mooncake version to 0.3.8.post1

[ShangmingCai]

Motivation

This version will fix #16502.

And I will revert the dockerfile change later in #16572 for safe.

Modifications

Accuracy Tests

Benchmarking and Profiling

Checklist

• Format your code according to the Format code with pre-commit.
• Add unit tests according to the Run and add unit tests.
• Update documentation according to Write documentations.
• Provide accuracy and speed benchmark results according to Test the accuracy and Benchmark the speed.
• Follow the SGLang code style guidance.

Review Process

1. Ping Merge Oncalls to start the PR flow. See the PR Merge Process.
2. Get approvals from CODEOWNERS and other reviewers.
3. Trigger CI tests with comments or contact authorized users to do so.
   • /tag-run-ci-label, /rerun-failed-ci, /tag-and-rerun-ci
4. After green CI and required approvals, ask Merge Oncalls to merge.

[gemini-code-assist]

Summary of Changes

Hello @ShangmingCai, 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 a dependency upgrade for mooncake-transfer-engine to version 0.3.8.post1. This update is crucial for resolving a specific issue and ensures that development, CI, and runtime environments consistently use the corrected version of the library. The changes are confined to updating version strings in relevant configuration and installation files.

Highlights

• Dependency Update: The mooncake-transfer-engine dependency has been updated from version 0.3.8 to 0.3.8.post1 across various configuration and installation scripts.
• Bug Fix Reference: This version bump is intended to address and fix an issue detailed in sgl-project/sglang/pull/16502.
• Version Requirement Alignment: The minimum required Mooncake version mentioned in a warning message for the tensor allocator has been updated to 0.3.8.post1 to reflect the new dependency.

🧠 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.

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. ↩

[ShangmingCai]

/tag-and-rerun-ci

[gemini-code-assist]

Code Review

This pull request bumps the version of mooncake-transfer-engine to 0.3.8.post1 across the codebase, including the Dockerfile, CI scripts, and a warning message in the source code. The changes are consistent and correct. I've added one suggestion to improve a warning message to use the correct package name, which will help users avoid confusion.

[ShangmingCai]

H20 disaggregation tests have passed.