Fix stale MCP tools list after failed connection retest in Add/Edit Instance dialog - #576
Merged
haiphucnguyen merged 1 commit intoJul 28, 2026
Conversation
haiphucnguyen
approved these changes
Jul 28, 2026
haiphucnguyen
left a comment
haiphucnguyen
left a comment
Collaborator
There was a problem hiding this comment.
Thank you @frank-1802
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
2 participants
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.
When testing MCP connection settings in the Add/Edit Instance dialog, previously discovered tools could remain visible even after a later test failed due to invalid config changes.
Behavior after this change. The dialog now reflects the latest test result consistently: