Closed yenshirak closed 1 year ago
Thanks for reporting! I was finally able to reproduce it locally. Will ship a fix soon.
Okay, fixed here https://github.com/anycable/anycable-go/commit/e8fd29c217e813d7fb367f6d7bf11864f3954f8a. Available in the edge image today, or in the upcoming release (~Thu-Fri).
Great, thank you!
Tell us about your environment
AnyCable-Go version: 1.4.2
AnyCable gem version: 1.4.1
We use the redisx broadcast adapter, the memory broker and the actioncable-v1-ext-json protocol, 1 anycable-go instance, no pub/sub. JWT authentication is enforced, we don't use RPC.
What did you do?
We upgraded to 1.4.2 and switched to the actioncable-v1-ext-json protocol.
What did you expect to happen?
No panics.
What actually happened?
The anycable-go service still panics but it seems less frequent:
Please let me know if you need any additional info or help with debugging and fixing the issue.