Closed barriehadfield closed 6 years ago
@janbiedermann thinks this is the client code sending a nil value. I will leave the issue open until we resolve it.
I made hyper operation more robust here, as you suggested, as i believe it is a valid condition, that a channel may have no connections. I have seen this issue before, same place, with ActionCable. This issue may indicate a connection setup problem. This problem may now show up on the client in a different way, we will see.
gem 'hyper-operation', git: 'https://github.com/ruby-hyperloop/hyper-operation.git', branch: '1_0_0'
seems to do it
We are only seeing this issue on Heroku (does not happen on a local instance). I have tested changing the transport to :simple_poller and all is fine, so it only happens with :pusher as the transport.