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.

Sign up for GitHub

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

Jump to bottom

Propagate Rst/GoAway as distinct errors #16

Closed
nitely opened this issue Jul 11, 2024 · 0 comments · Fixed by #34
Closed

Propagate Rst/GoAway as distinct errors #16

nitely opened this issue Jul 11, 2024 · 0 comments · Fixed by #34

Comments

@nitely
Copy link
Owner

nitely commented Jul 11, 2024 •
edited
Loading

Application code have no way to check/catch if an error is local or remote. It should be a field typ(e) with enum of localErr/remoteErr so the type is not lost by assigning the error to the Client/Stream object.
@nitely nitely mentioned this issue Jul 13, 2024
Merged
nitely added a commit that referenced this issue Jul 13, 2024
@nitely
Propagate RST errors (#17)
1a70e8c 
fixes part of #16
@nitely nitely mentioned this issue Dec 18, 2024
Merged
@nitely nitely closed this as completed in 315d243 Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Propagate GoAway errors nitely/nim-hyperx
1 participant
@nitely