[jira] [Created] (TINKERPOP-2846) Different Behavior in Response to Close Frames in Python

["Cole Greer (Jira)" <ji...@apache.org>]

Cole Greer created TINKERPOP-2846:
-------------------------------------

             Summary: Different Behavior in Response to Close Frames in Python
                 Key: TINKERPOP-2846
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2846
             Project: TinkerPop
          Issue Type: Improvement
          Components: python
    Affects Versions: 3.7.0
            Reporter: Cole Greer


Typically if a gremlin client receives a close websocket frame from the server, it will mark the current connection as dead, and attempt to create a new connection. The python GLV does not replicate this behavior, it appears that upon receiving a close web socket frame, the underlying asyncio event loop in the transporter is closed and no attempt to reconnect is made. Further, awareness of this closed state does not propagate back up to the client level as client.is_closed() will still return false. Any future requests made through this client will fail as the underlying event loop is closed. In the near future, I will be submitting a PR as part of [TINKERPOP-2819|https://issues.apache.org/jira/browse/TINKERPOP-2819] which contains a test demonstrating this behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)