Skip to content
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

Consider adding spec tests for System.IO.Pipelines #27847

Closed
jkotalik opened this issue Nov 7, 2018 · 2 comments
Closed

Consider adding spec tests for System.IO.Pipelines #27847

jkotalik opened this issue Nov 7, 2018 · 2 comments
Labels
area-System.IO.Pipelines backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity test-enhancement Improvements of test source code

Comments

@jkotalik
Copy link
Contributor

jkotalik commented Nov 7, 2018

In AspNetCore 3.0, we will be exposing Pipes directly across our stack as part of the HttpContext. To do this, we need to create a Stream to Pipe adapter (Pipe that wraps a Stream). It would be nice to have spec tests for System.IO.Pipelines such that our adapted implementation is compliant.

cc @pakrym @davidfowl

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 23, 2020
@BrennanConroy BrennanConroy removed the untriaged New issue has not been triaged by the area owner label Jul 8, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels Jan 8, 2025
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.IO.Pipelines backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity test-enhancement Improvements of test source code
Projects
None yet
Development

No branches or pull requests

4 participants