Make Streamable HTTP status mapping deterministic - #1797
Open
halter73 wants to merge 1 commit into
Open
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This intentionally leaves quiet 2026-07-28 handlers subject to the caller's
HttpClienttimeout unless they emit an inline message such as progress. It does not addStartResponseAsync; a Streamable HTTP-only API onRequestContext<T>needs a separate design.Validation
dotnet buildpasses with 0 warnings and 0 errorsDockerEverythingServerTests.Sampling_Sse_EverythingServerremains environment-blocked because the configured running server does not exposetrigger-sampling-request; the restored npm everything-server integration tests passNote
This pull request description was generated with GitHub Copilot.