-
Notifications
You must be signed in to change notification settings - Fork 431
fix(server): stop per-session toolsets on session delete #3884
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
Open
EronWright
wants to merge
1
commit into
docker:main
Choose a base branch
from
EronWright:contrib/stop-toolsets-on-delete
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+78
−11
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[medium]
BatchDeleteSessionsnew drain goroutine cannot be awaited viaWaitStoppedThe PR adds an asynchronous goroutine in
BatchDeleteSessionsthat waits for the session stream to drain and then callssm.stopSessionToolSets— the same teardown work thatDeleteSessiondoes. However, unlikeDeleteSession(which stores the runtime indeletedSessionsbefore returning),BatchDeleteSessionsnever callssm.deletedSessions.Store(sessionID, sessionRuntime).WaitStoppedreads exclusively fromdeletedSessions:So a caller that does
BatchDeleteSessions(...)followed byWaitStopped(sessionID, ...)will receive an immediatenileven while the new drain goroutine is still running (waiting to drain the stream and callStopToolSets). Before this PR there was nothing to wait for inBatchDeleteSessions, but now there is — and the wait contract is silently broken.Impact: Any consumer that uses
WaitStoppedto synchronise on full teardown (e.g. to confirm MCP subprocesses have exited) after a batch delete will get a false-complete signal. Consider mirroringDeleteSession'sdeletedSessions.Storecall inBatchDeleteSessions(and having the drain goroutine calldeletedSessions.Deletewhen done), or documenting thatWaitStoppedis not supported after batch deletes.