Skip to content

fix: space conformance progress notifications - #329

Merged
jeanmatthieu merged 1 commit into
modelcontextprotocol:mainfrom
EhsanAzish80:fix/conformance-progress-timing
Nov 10, 2026
Merged

jeanmatthieu merged 1 commit into
modelcontextprotocol:mainfrom
EhsanAzish80:fix/conformance-progress-timing

Conversation

@EhsanAzish80

Copy link
Copy Markdown
Contributor

Motivation and Context

The shared conformance server sends progress notifications 50 microseconds apart, while the conformance scenario expects about 50 milliseconds. The test can receive only one or two notifications before the tool result. I reproduced this on main, so this is separate from #307. This changes the two fixture delays to 50 milliseconds.

How Has This Been Tested?

  • On unchanged main, the progress scenario failed 2 of 5 runs. With this change, it passed 10 of 10 runs with all three notifications.
  • swift test: 580 passed.
  • scripts/run-conformance.sh --mode server: 47 passed, 0 failed.

Breaking Changes

None. This only changes the conformance server fixture.

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

reviewed the diff and ran the tests.

@EhsanAzish80
EhsanAzish80 requested a review from a team as a code owner November 10, 2026 08:26

@jeanmatthieu jeanmatthieu left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Good catch 👏

@jeanmatthieu
jeanmatthieu merged commit 3059fd5 into modelcontextprotocol:main Nov 10, 2026
6 checks passed
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