Robert Elwell

What's the status on this? I'm surprised to see this doesn't work.

It's been eight months since I dropped my last comment into this issue, and I've had to essentially monkey-patch the async file for all this time. This seems to me...

@RoryOfByrne here's a gist of my workaround: https://gist.github.com/relwell/3eb9d68526ba8eadb41b3b1399e747a9 you would import that file instead of the normal zappa_async module.

I think so, @RoryOfByrne. It's been a while since I inspected the solution.

What can we do to get this one completed and merged?

Python 2 is a few months away from EOL. It's very frustrating to see this PR still open. What needs to be done to get this merged?

Cleaning out my open issues.

@rmosolgo I think the `README` for this library merits a deprecation warning. I spent a couple hours this morning digging into this exact problem. If your recommendations in https://github.com/rmosolgo/graphql-ruby/issues/2398 were...

I'm having this same problem, as soon as I push a message. The thing that is strange to me is that there doesn't seem to be adequate error reporting around...

I managed to do some more debugging and I think I see the problem. There's an error on the Elixir side, so I'm guessing the server is closing the channel....