Downgrade "No callback for response message" from Warning to Debug in OutsideRuntimeClient

[Copilot]

When a client cancels an IAsyncEnumerable enumerator, the server still sends a response after the client has already removed the callback — producing frequent, noisy Warning logs that are entirely expected behavior.

Changes

• OutsideRuntimeClient.cs: Change log level for "No callback for response message" from LogLevel.Warning → LogLevel.Debug, matching the identical log already at Debug in InsideRuntimeClient.cs. Renamed method from LogWarningNoCallbackForResponseMessage → LogDebugNoCallbackForResponseMessage for consistency.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Frequent warning logs due to client-side cancellation of an IAsyncEnumerable enumerator</issue_title>
<issue_description>With the update to Orleans 10, I now have a noticeably increased warning rate on the (outside) Orleans clients.

No callback for response message '"IsAlwaysInterleave Response [/grain/]->[ /client/] (Canceled, ) #3F2A2E365932F362"'

I agree with Copilot's analysis that this response message is the value tuple from AsyncEnumerableExtension due to the server-side half of cancellation and that it is received by a client that has already cleaned up the the message from the callback dictionary due to its own, initiated cancellation.</issue_description>

<agent_instructions>convert this to a debug log</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@ReubenBond Thanks for reporting @Tragetaschen. We should convert this to a debug log, since it's expected. I'll have copilot do it now.

• Fixes Frequent warning logs due to client-side cancellation of an IAsyncEnumerable enumerator #9949

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Microsoft Reviewers: Open in CodeFlow

[ReubenBond]

@copilot Also make this change in InsideRuntimeClient

[Copilot]

@copilot Also make this change in InsideRuntimeClient

InsideRuntimeClient already has the equivalent log (LogDebugNoCallbackForResponse) at LogLevel.Debug — it was never at Warning. The Warning was only in OutsideRuntimeClient, which is now fixed in f247a87.

[Copilot]

Pull request overview

Adjusts logging in OutsideRuntimeClient to reduce expected warning noise when clients cancel IAsyncEnumerable enumerations and a late response arrives without a registered callback.

Changes:

• Downgrade “No callback for response message …” log from Warning to Debug in OutsideRuntimeClient.
• Rename the logger helper method to reflect the new log level (LogWarning… → LogDebug…).