You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Order notification round-trip test by server-set LastUpdatedAt
The server emits the Working and Completed notifications in strict order
(each SendTaskStatusNotificationAsync awaits the transport write), but the
client-side McpSessionHandler dispatches each incoming message via a
fire-and-forget Task with a forced thread-pool yield, so user-registered
notification handlers may observe them out of receipt order. Net10's
thread-pool scheduling exposed this race intermittently.
Give the two notifications distinct LastUpdatedAt values on the server
and sort by that timestamp before asserting types/payloads, so the test
asserts the round-trip without depending on client-side dispatch order.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@@ -665,22 +670,25 @@ public static async Task<string> RootsTool(McpServer server, CancellationToken c
665
670
[McpServerTool(Name="notifying-tool"),System.ComponentModel.Description("A tool that emits SendTaskStatusNotificationAsync from inside the task wrapper")]
0 commit comments