Skip to content

test: fix progress notification assertions for related_request_id#2038

Open
akshan-main wants to merge 2 commits intomodelcontextprotocol:mainfrom
akshan-main:bugfix/progress-notification-missing-metadata
Open

test: fix progress notification assertions for related_request_id#2038
akshan-main wants to merge 2 commits intomodelcontextprotocol:mainfrom
akshan-main:bugfix/progress-notification-missing-metadata

Conversation

@akshan-main
Copy link

@akshan-main akshan-main commented Feb 11, 2026

Summary

Fixes failing CI after #2002 added related_request_id to progress notifications.

The report_progress() method now passes related_request_id=self.request_id to send_progress_notification(), but the test in test_176_progress_token.py was not updated to expect this new argument. This caused all 20 test matrix jobs to fail.

Updated the three assert_any_call assertions to include related_request_id="test-request". Added unit test

hubbard-zlee and others added 2 commits February 5, 2026 12:22
Progress notifications were not being delivered to clients because
related_request_id was not passed to send_progress_notification(),
causing the SSE transport to drop the notification.
Update existing test assertions to include related_request_id, and add
a dedicated test verifying that report_progress() correctly passes the
request_id as related_request_id to send_progress_notification().
@akshan-main akshan-main force-pushed the bugfix/progress-notification-missing-metadata branch from 1ff495b to e4f97e4 Compare February 11, 2026 20:26
@akshan-main
Copy link
Author

@maxisbey

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