Skip to content

Improve TestServer support for Response.StartAsync #10189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 13, 2019

Conversation

JamesNK
Copy link
Member

@JamesNK JamesNK commented May 12, 2019

Addresses #8660

re: #8660 (comment)

@JamesNK JamesNK requested a review from Tratcher May 12, 2019 09:10
@JamesNK JamesNK requested a review from analogrelay as a code owner May 12, 2019 09:10
@analogrelay analogrelay added this to the 3.0.0-preview6 milestone May 12, 2019
Copy link
Member

@Tratcher Tratcher left a comment

Choose a reason for hiding this comment

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

Yeah, that's right. OnStarting exceptions are considered fatal in all servers, but in Test Server we make a point of flowing any useful exception directly to the client so we can debug it.

That test was added after we found that pattern causing a deadlock with large data filling the pipe. It was real issue for the MVC tests. Feel free to clarify the naming but it's not wrong.

@JamesNK JamesNK merged commit d5207af into master May 13, 2019
@ghost ghost deleted the jamesnk/testserver-startasync branch May 13, 2019 10:38
@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares and removed area-runtime labels Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants