We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now Send() just silently eats the send by doing a null check on connection, and catches io and socket exceptions.
I think it should throw so any requests are not lost into ether (and I think async jobs will not resolve/fail until the next disconnect).
No response
.NET Core or .NET 5 or higher.
6
The text was updated successfully, but these errors were encountered:
Additional diagnostics available in #1102
Sorry, something went wrong.
No branches or pull requests
What did you expect to happen?
Right now Send() just silently eats the send by doing a null check on connection, and catches io and socket exceptions.
Instead of that, what actually happened?
I think it should throw so any requests are not lost into ether (and I think async jobs will not resolve/fail until the next disconnect).
Which operating system are you running on?
No response
Which .NET Runtime are you running on?
.NET Core or .NET 5 or higher.
Version
6
Relevant log output
No response
Example Code
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: