Open JamesNK opened 2 years ago
Thanks for contacting us.
We're moving this issue to the .NET 7 Planning
milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
@JamesNK can you please investigate this one?
I believe it is a bug in S.N.Q
Logged issue: https://github.com/dotnet/runtime/issues/71927
@JamesNK Should this also get moved to 8 now that the runtime issue has been moved?
Thanks for contacting us.
We're moving this issue to the .NET 8 Planning
milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
Is there an existing issue for this?
Describe the bug
I noticed in logs that Kestrel logs a BadRequest event after a request is finished. From gRPC benchmarks.
Interesting bit:
Expected Behavior
No exception when request completes gracefully
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response