Skip to content

Conversation

taobaorun
Copy link

Motivation and Context

#502

How Has This Been Tested?

Tested 24 hours, Client received all messages.

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

@taobaorun taobaorun changed the title fix SseLineSubscriber will not request after default 256 request fix:SseLineSubscriber will not request after default 256 request Aug 20, 2025
@taobaorun taobaorun changed the title fix:SseLineSubscriber will not request after default 256 request fix: SseLineSubscriber will not request after default 256 request Aug 20, 2025
@tzolov tzolov added this to the 0.12.0 milestone Aug 20, 2025
@tzolov tzolov self-assigned this Aug 20, 2025
@tzolov
Copy link
Contributor

tzolov commented Aug 20, 2025

Thanks for addressing this @taobaorun !

@tzolov
Copy link
Contributor

tzolov commented Aug 25, 2025

@taobaorun i believe this #507 better addresses the issue as it excludes the error case

@tzolov
Copy link
Contributor

tzolov commented Aug 25, 2025

Resolved by #507

@tzolov tzolov closed this Aug 25, 2025
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.

3 participants