Fix Semaphore release Issue in api_generate_stream Function of vllm_worker
#3390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
When you have a moment. Could you please take a look at this PR? @merrymercy @infwinston @BabyChouSr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
This PR addresses a potential issue in the
api_generate_streamfunction where the semaphore might not be properly released in all scenarios. Specifically, if an exception occurs during the execution ofworker.generate_stream(params), thecreate_background_tasks(request_id)function might not be called. This could lead to the semaphore not being properly released.Related issue number (if applicable)
Closes #3389
Checks
format.shto lint the changes in this PR.