refactor: extract tool fetch loop body for safe cleanup - #319
Open
IbrahimAhmed8 wants to merge 1 commit into
Open
refactor: extract tool fetch loop body for safe cleanup#319IbrahimAhmed8 wants to merge 1 commit into
IbrahimAhmed8 wants to merge 1 commit into
Conversation
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
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.
In internal/node/mcp_handlers.go, fetchRemoteToolCatalogue now ensures cleanup occurs per iteration.
The previous implementation was functionally correct but introduced a latent risk. If session.ListTools panics or if a conditional return is introduced later, active streams and sessions would leak
Changes:
Extracted the loop body into a helper method named fetchToolsForRemoteService. This scopes the defer statement to the iteration scope rather than the parent function scope.
A standard defer inside the loop was intentionally avoided to prevent holding all network streams open until function return