Connection ack error when keep alive message arrives first about gql

[leszekhanusz]

Websockets are indeed done on top of TCP.
What may be confusing is that there is two types of keep alive at different levels of the network model.

The Keep-Alive in the transport level are managed by the TCP stack of the operating system. We don't see them in our code.

The keep alive we are talking about here are simply message exchanged in the application level. This is an optional feature of the different GraphQL servers.

[leszekhanusz]

Thank you for your bug report.
Could you please check that the PR #110 solves your problem ?

[hugbubby]

Thank you for your bug report.
Could you please check that the PR #110 solves your problem ?

How do you replace your local version of gql in a python venv with the version from this pull request?

Edit: Figgered it out, WFM in client creation but still debuggging some further errors down the line

[KingDarBoja]

Not well versed on webscokets but as far as I know, it uses TCP (Transmission Control Protocol) which is the one that sends the Keep-Alive messages and is causing this issue. A good resource to understand for anyone willing to learn is appsync-websockets-python (from AWS).

Reviewing right now the linked PR, this should be release with the next beta version.