Skip to content

Conversation

@vorburger
Copy link

Motivation and Context

Catch the root cause of #605 earlier if it ever happens again in the future.

How Has This Been Tested?

Not really, but hopefully it's safe; I would welcome code review!

Breaking Changes

Nope, this is an internal change for safety, which (hopefully) should have no impact.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@tzolov do you think this makes sense? I'm proposing this as a follow-up (NOT an alternative) to #607 (and #657), which IMHO makes sense either way as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant