[PP] put pp assert in model runner#12934
Conversation
Signed-off-by: Xuchun Shang <xuchun.shang@gmail.com>
Summary of ChangesHello @XucSh, I'm Gemini Code Assist1! 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 refines the handling of pipeline parallelism within the SGLang runtime by improving error reporting and type safety. It centralizes an important assertion to ensure that pipeline parallelism is only enabled for models that explicitly support it, making debugging easier. Additionally, it updates function signatures to correctly reflect the data types returned when pipeline parallelism is active, enhancing code clarity and maintainability. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request improves error handling by moving an assertion for pipeline parallelism support to the ModelRunner's initialization, which is a good change for fail-fast behavior. The related type hints have also been updated. I've added a few suggestions to further improve type safety and code readability by adding type hints for the pp_proxy_tensors argument in several methods.
| @@ -2056,7 +2061,7 @@ def forward_decode( | |||
| forward_batch: ForwardBatch, | |||
| skip_attn_backend_init: bool = False, | |||
| pp_proxy_tensors=None, | |||
| @@ -2079,7 +2084,7 @@ def forward_extend( | |||
| forward_batch: ForwardBatch, | |||
| skip_attn_backend_init: bool = False, | |||
| pp_proxy_tensors=None, | |||
| @@ -2106,7 +2111,7 @@ def forward_extend( | |||
|
|
|||
| def forward_idle( | |||
| self, forward_batch: ForwardBatch, pp_proxy_tensors=None | |||
There was a problem hiding this comment.
To improve type safety and code readability, please add a type hint for the pp_proxy_tensors argument. It should be Optional[PPProxyTensors].
| self, forward_batch: ForwardBatch, pp_proxy_tensors=None | |
| self, forward_batch: ForwardBatch, pp_proxy_tensors: Optional[PPProxyTensors] = None |
Signed-off-by: Xuchun Shang <xuchun.shang@gmail.com>
Motivation
put the assert in model runner to make error more clear
Checklist