Skip to content

Harden driver against unexpected RESET responses #1006

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

Merged
merged 2 commits into from
Dec 27, 2023

Conversation

robsdedude
Copy link
Member

The server has been observed to reply with FAILURE and IGNORED to RESET requests. The former is according to spec and the driver should drop the connection (which it didn't), the latter isn't.

The right combination of those two unexpected responses at the right time could get the driver stuck in an infinite loop.

This change makes the driver drop the connection in either case to gracefully handle the situation.

The server has been observed to reply with `FAILURE` and `IGNORED` to `RESET`
requests. The former is according to spec and the driver should drop the
connection (which it didn't), the latter isn't.

The right combination of those two unexpected responses at the right time could
get the driver stuck in an infinite loop.

This change makes the driver drop the connection in either case to gracefully
handle the situation.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

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

🦝

(Unit tests are more than welcome :D )

@robsdedude robsdedude merged commit 23cce6a into neo4j:5.0 Dec 27, 2023
@robsdedude robsdedude deleted the harden-agains-failing-reset branch December 27, 2023 07:52
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.

2 participants