Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR addresses issues with session closing logic in the lmdeploy session manager and includes additional CMake build configuration improvements. The main focus is on fixing how sessions are closed to prevent premature cancellation and ensure proper resource cleanup when the main program exits.
Changes:
- Enhanced the
Session.close()method to wait for async operations to complete with a 5-second timeout - Added early exit optimization for sessions that haven't processed any requests yet
- Improved error logging in async_close() to use logger.exception()
- Wrapped test executables in BUILD_TEST conditionals in two CMakeLists.txt files
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| lmdeploy/serve/managers/session_manager.py | Main fix: Added synchronization to close() method to wait for async operations, early return for unused sessions, and improved error logging |
| src/turbomind/kernels/CMakeLists.txt | Wrapped test_quantization executable in BUILD_TEST conditional |
| src/turbomind/comm/gloo/CMakeLists.txt | Wrapped test_ipc_comm executable in BUILD_TEST conditional |
Comments suppressed due to low confidence (1)
lmdeploy/serve/managers/session_manager.py:128
- The abort() method doesn't wait for the async operation to complete, unlike the new close() implementation. This inconsistency could lead to race conditions where abort() returns before the async_abort() coroutine finishes executing. While the async_abort() method has a comment indicating "DO NOT reset the session here because it might be used by other components," the lack of synchronization in abort() could still cause issues if the caller expects the abort operation to complete before proceeding.
Consider applying similar synchronization logic to abort() as was added to close(), or document why abort() doesn't need to wait for completion while close() does.
def abort(self):
"""Abort the session in sync mode."""
self._run(self.async_abort())
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
f4b69e4 to
a87164a
Compare
This file contains hidden or 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
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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist