You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's what's weird—we haven't made any recent changes.
What did you expect to happen?
No exceptions 😄
What actually happened?
NoMethodError: undefined method `env' for nil:NilClass Did you mean? end
def call(_method, request, meta)
return yield unless meta["sid"]
request.env.sid = meta["sid"]
yield
env_sid.rb 9 call(...)
[GEM_ROOT]/gems/anycable-core-1.3.0/lib/anycable/middlewares/env_sid.rb:9:in `call'
Unfortunately I do not have a reproduction for you. This only started yesterday and we've only had 146 of these errors sporadically happen. At peak times we have ~2.7k connected clients. My assumption is that in these cases, the websocket connection will fail and the js client will attempt reconnect, so at least customer impact should be minimal or nonexistent. But I am confused. Why did this start now? We haven't introduced new channels or new websocket functionality or any infrastructure changes (at least not as far as I'm aware of).
Have you seen anything like this before? Should I be more concerned?
The text was updated successfully, but these errors were encountered:
Tell us about your environment
Ruby version: 2.7.7p221
anycable
gem version: 1.3.0anycable-rails
gem version: 1.3.7grpc
gem version: 1.47.0What did you do?
That's what's weird—we haven't made any recent changes.
What did you expect to happen?
No exceptions 😄
What actually happened?
Unfortunately I do not have a reproduction for you. This only started yesterday and we've only had 146 of these errors sporadically happen. At peak times we have ~2.7k connected clients. My assumption is that in these cases, the websocket connection will fail and the js client will attempt reconnect, so at least customer impact should be minimal or nonexistent. But I am confused. Why did this start now? We haven't introduced new channels or new websocket functionality or any infrastructure changes (at least not as far as I'm aware of).
Have you seen anything like this before? Should I be more concerned?
The text was updated successfully, but these errors were encountered: