Skip to content

Test and fix #52 #53

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

Merged
merged 4 commits into from
Mar 26, 2025
Merged

Test and fix #52 #53

merged 4 commits into from
Mar 26, 2025

Conversation

AbdullatifGhajar
Copy link
Contributor

include a test to reproduce the issue #52 and solve it

Motivation and Context

SSE client can't connect to an SSE server because of wrong url handling

How Has This Been Tested?

An integration test has been written, in which an SSE client should successfully connect to an SSE server without mocking

Breaking Changes

No breaking changes

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

@e5l e5l self-requested a review March 14, 2025 07:56
Copy link
Contributor

@e5l e5l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please check the comment

@@ -39,7 +39,7 @@ public class SseClientTransport(
private var job: Job? = null

private val baseUrl by lazy {
session.call.request.url.toString().removeSuffix("/")
session.call.request.url.toString().removeSuffix("/sse")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to keep the prefix to have an explicit URL, but use the correct URL concatenation method to avoid duplicate // in path segments. There are several methods for pathSegment in Ktor you can use or build your own.

@e5l e5l self-requested a review March 26, 2025 08:27
Copy link
Contributor

@e5l e5l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm as discussed

@e5l e5l enabled auto-merge (squash) March 26, 2025 08:27
@e5l e5l merged commit be4f9c3 into modelcontextprotocol:main Mar 26, 2025
1 check passed
@AbdullatifGhajar AbdullatifGhajar deleted the #52-fix branch March 26, 2025 16:19
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.

2 participants