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
andIGNORED
toRESET
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.
Backport of: https://github.com/neo4j/neo4j-python-driver/pull/1006