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

Set connection status to ERROR when closed due to protocol error (#126) #127

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ada-waffles
Copy link

Set connection status to ERROR when closed due to protocol error

Motivation:

Addresses #126

Modifications:

  • Amends DuplexConnection#close to accept an optional error indicating that the connection is being closed due to that error
  • Updates implementations to handle this error and report it to consumers
  • Updates RSocketMachine to pass protocol-level connection errors to close
  • Adds/updates tests to check for handling this parameter

Result:

Protocol-level errors will forward the error through the new error parameter in DuplexConnection#close, resulting in ERROR status instead of CLOSED

Amends DuplexConnection#close to accept an optional error indicating that the connection is being closed due to that error.

Updates implementations to handle this error and report it to consumers.

Updates RSocketMachine to pass protocol-level connection errors to close

Adds/updates tests to check for handling this parameter

Signed-off-by: Stephen Cohen <stesen@outlook.com>
@ada-waffles ada-waffles force-pushed the bugfix/connection-error-status branch from 6254847 to a03b173 Compare April 26, 2021 02:13
@viglucci
Copy link
Member

viglucci commented May 6, 2021

Hi @duke9509!

Thanks for filing #126 and for providing this PR. While I'm not able to offer a timeframe at the moment, we'll do our best to get this reviewed.

Thanks again!

Copy link
Member

@viglucci viglucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this seems pretty tame and a good approach, however, I did have two questions. I would be interested to hear any thoughts from those more experienced with the project, such as @OlegDokuka.

@viglucci
Copy link
Member

My questions were answered and everything turned out to be non-issues. I pinged some maintainers with write permissions to hopefully take a look and give a final approval/merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants