-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Report cause for Akka/IO TCP CommandFailed events #6221
Report cause for Akka/IO TCP CommandFailed events #6221
Conversation
public CommandFailed WithCause(Exception cause) | ||
{ | ||
// Needs to be added with a mutable property for compatibility reasons | ||
return new CommandFailed(Cmd) { Cause = cause }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this holds true in C# or we could just add a second constructor instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could just add a constructor overload and that would work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I think this is probably a fine way of doing it
8aa5df2
to
efc6069
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@Arkatufus can we backport to v1.4? |
…6224) * Port [#22954](akka/akka#22954) ## Changes > I think we should finally fix this once and forever. We have so many failed test jobs where we cannot be sure why "Connect failed" and we have no way of finding out without enabling DEBUG log level everywhere. That same pain is felt by every user. (cherry-picked from c9c0b44) * Update API Verify list Co-authored-by: Ismael Hamed <1279846+ismaelhamed@users.noreply.github.com>
Port #22954
Changes
Checklist
For significant changes, please ensure that the following have been completed (delete if not relevant):