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

[QUIC] Surface transport error code in QuicException #72666

Closed
Tracked by #82262
ManickaP opened this issue Jul 22, 2022 · 4 comments
Closed
Tracked by #82262

[QUIC] Surface transport error code in QuicException #72666

ManickaP opened this issue Jul 22, 2022 · 4 comments
Assignees
Milestone

Comments

@ManickaP
Copy link
Member

ManickaP commented Jul 22, 2022

In case of SHUTDOWN_INITIATED_BY_TRANSPORT we now get transport level error code, but we don't use it.

We also get it in SHUTDOWN_COMPLETE.ConnectionShutdown case where we would throw the same exception as in SHUTDOWN_INITIATED_BY_TRANSPORT in ideal case.

There might still be necessity to expand msquic data to avoid holding stream -> connection link to solve this properly.

https://www.rfc-editor.org/rfc/rfc9000.html#name-transport-error-codes

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 22, 2022
@ghost
Copy link

ghost commented Jul 22, 2022

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

In case of SHUTDOWN_INITIATED_BY_TRANSPORT we now get transport level error code, but we don't use it.

We also get it in SHUTDOWN_COMPLETE.ConnectionShutdown case where we would throw the same exception as in SHUTDOWN_INITIATED_BY_TRANSPORT in ideal case.

There might still be necessity to expand msquic data to avoid holding stream -> connection link to solve this properly.

Author: ManickaP
Assignees: -
Labels:

area-System.Net.Quic

Milestone: -

@ManickaP ManickaP added this to the 8.0.0 milestone Jul 22, 2022
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 22, 2022
@ManickaP
Copy link
Member Author

Triage: in the same bucket as other exception related issues, should be investigated and decided in 8.0.

@karelz
Copy link
Member

karelz commented Jul 18, 2023

@wfurt shouldn't this be resolved by your changes?

@wfurt
Copy link
Member

wfurt commented Jul 18, 2023

fixed by #88550 (community contribution)

@wfurt wfurt closed this as completed Jul 18, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants