Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Interesting. This happens every time? You can try to switch to EventMachine as a workaround, but of course it's not a "solution".
Can you post your code somewhere?
This looks suspicious. The error is displayed in Slack? It feels like those two are unrelated, try to isolate the pieces? Basically we want a stack trace from the error.
So `connect!` is failing, but we're getting the wrapper (actor crashed) error. Maybe add some code to `Slack::RealTime::Concurrency::Celluloid::Socket#connect!` to get a better exception from in there? (that code would be...
It seems like faye-websocket supports proxies, documented in https://github.com/faye/websocket-driver-ruby#http-proxies. We instantiate the client [here](https://github.com/slack-ruby/slack-ruby-client/blob/master/lib/slack/real_time/client.rb#L114), so it just needs the right options exactly as you've been passing them in. So you...
Agreed @newdark, that should be fixed independently, want to give it a shot?
I mean getting a better exception would be a good start.
I think we still have an issue with proxies and RTM connections, so I'll reopen this.
This is a problem. We [wrap](https://github.com/slack-ruby/slack-ruby-client/blob/018dcfdea5a4bfb63310ac16e0dfceb1827816f4/lib/slack/real_time/models/base.rb#L4) responses with a `Hashie::Mash` and what you're getting is the size of the hash instead of the value in it. You should write a...
I think we don't want this by default. Did you figure out a way to do this in your own code? I would like us to document how to do...