Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry pick #776 #779 #788 #789 #794 to release branch #803

Closed

Conversation

Jeffwan
Copy link
Collaborator

@Jeffwan Jeffwan commented Mar 6, 2025

Pull Request Description

#776 #779 #788 #789 #794 to better support deepseek and api compatibility

Related Issues

Resolves: #[Insert issue number(s)]

Important: Before submitting, please complete the description above and review the checklist below.


Contribution Guidelines (Expand for Details)

We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

  • [Bug]: Corrections to existing functionality
  • [CI]: Changes to build process or CI pipeline
  • [Docs]: Updates or additions to documentation
  • [API]: Modifications to aibrix's API or interface
  • [CLI]: Changes or additions to the Command Line Interface
  • [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

  • PR title includes appropriate prefix(es)
  • Changes are clearly explained in the PR description
  • New and existing tests pass successfully
  • Code adheres to project style and best practices
  • Documentation updated to reflect changes (if applicable)
  • Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

varungup90 and others added 6 commits March 6, 2025 09:33
* Ignore worker pods for gateway routing
* ignore worker pods in UpdatePod as well
* use node worker as const

Signed-off-by: Varun Gupta <[email protected]>
fix env error caused by helm set command, use —set-string for env bool

Signed-off-by: Jiaxin Shan <[email protected]>
* Make stream include usage as optional

---------

Signed-off-by: Varun Gupta <[email protected]>
It helps to only consider the engine pod for multi-node inference. Ray worker doesn’t have http server running and it can not expose any application but only resource metrics. For resource metrics, since we use Tensor Parallelism, we think the utilization across GPU are same.

Signed-off-by: Jiaxin Shan <[email protected]>
…ect#794)

Update request message processing for prompt input

Signed-off-by: Varun Gupta <[email protected]>
@Jeffwan
Copy link
Collaborator Author

Jeffwan commented Mar 6, 2025

I will rebase test change #805 and make sure cherry-pick pass the test.

Enable tests for release branch

Signed-off-by: Jiaxin Shan <[email protected]>
@Jeffwan Jeffwan closed this Mar 6, 2025
@Jeffwan Jeffwan reopened this Mar 6, 2025
@Jeffwan
Copy link
Collaborator Author

Jeffwan commented Mar 6, 2025

seems it can not trigger the CI. I will create a new PR

@Jeffwan Jeffwan closed this Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants